Changes for page Tips and Tricks

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -11,7 +11,7 @@
11	11	* **More is better.** When in doubt, it is better to write one test too many than one test too few. Possible duplication is a lesser evil than not testing at all.
12	12	* **Keep test resources close to the tests** to make their use easy to understand. Test resources should be placed in the same location as the test if the resource is only needed by that test.
13	13	* **Avoid threads**
14		-** Concurrent programming is prone to introducing errors, very difficult to test and debug properly.
	14	+** Concurrent programming is prone to introducing errors and very difficult to test and debug properly.
15	15	** If threads are necessary, keep the amount of asynchronous code to a minimum.
16	16	** Separate synchronous and asynchronous logic to test them separately.
17	17	** Prefer thread termination conditions over fixed wait times, as this usually increases test performance dramatically.