[Esug-list] Concurrency Best Practices + Tests
tim at testit.works
Thu Sep 5 03:35:22 EDT 2019
Not to sound flippant - but do everything you can to limit where you use concurrency (and if possible, not at all). It adds lots of complication that often isn’t necessary.
Where you do need it, queue results or commands and then have workers to process those - workers, queues and commands put you back into easily testable territory.
Then you are left with the concurrent bit - hopefully now quite tiny and specific, which you you can normally blast and test if you have concurrency hole - but in the realms of can it queue things up in an orderly fashion and dequeue them as well. Deep code inspection on this is also helpful (albeit manual).
Sent from my iPhone
> On 4 Sep 2019, at 14:55, John M McIntosh <johnmci at smalltalkconsulting.com> wrote:
> John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk
> Sent from ProtonMail Mobile
>> On Wed, Sep 4, 2019 at 15:32, N. Bouraqadi <bouraqadi at gmail.com> wrote:
>> Hi everyone,
>> Can I get your input on the following questions :
>> - What are your best practices and recommendations for developing and testing concurrent software?
>> - How to discover need for synchronization/critical sections/ when doing TDD?
>> - How to write code to avoid dead-locks?
>> Thanks for your help,
>> Esug-list mailing list
>> Esug-list at lists.esug.org
> Esug-list mailing list
> Esug-list at lists.esug.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Esug-list