Changes for page Tips and Tricks

Summary

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

Details

Page properties

Content

...	...	@@ -10,7 +10,11 @@
10	10	* Use additional **simple high-level checks**. Use additional simple high-level checks. For example, when working with a collection, checking the number of elements is a good indicator of unexpected or missing elements.
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		-* **Avoid threads**, as concurrent programming is prone to errors, very difficult to test and debug properly. If threads are necessary, keep the amount of asynchronous code to a minimum. Also, separate synchronous and asynchronous logic to test them separately. Prefer thread termination conditions over fixed wait times, as this usually increases test performance dramatically.
	13	+* **Avoid threads**
	14	+** Concurrent programming is prone to errors, very difficult to test and debug properly.
	15	+** If threads are necessary, keep the amount of asynchronous code to a minimum.
	16	+** Separate synchronous and asynchronous logic to test them separately.
	17	+** Prefer thread termination conditions over fixed wait times, as this usually increases test performance dramatically.
14	14	* **Avoid files**
15	15	** I/O is slow increasing the test time unnecessarily.
16	16	** Temporary files may persist because you forgot to delete them or put them in folders where they will never be found. At the very least, be sure to delete files at the very beginning of the test to ensure their absence. Deleting files at the end of a test is prone to erros because if the test fails/aborts, those files may persist and affect subsequent tests.