Changes for page Tips and Tricks

Summary

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

Details

Page properties

Content

...	...	@@ -11,4 +11,42 @@
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	* Also **test non-functional aspects** such as security, single request computation performance, and perform load/stress testing to validate software throughput.
13	13	* **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.
14		-* **Avoid threads** if possible, as they are usually buggy and 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.
	14	+* **Avoid threads**, as they are usually buggy and 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.
	15	+* **Avoid files**
	16	+** I/O is slow increasing the test time unnecessarily.
	17	+** 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.
	18	+** Prefer data streams over files.
	19	+* **Don't leave tests unfinished**, don't just comment out @Test (annotation in Java to mark a function as a test), and don't leave empty test bodies as these things are confusing and waste the reader's time. If you come across this kind of code, try to learn its purpose, ask people who worked on it, and rebuild it. If that is not possible or worth the time, then delete it as the dead code that it is. To indicate that tests need to be implemented, an issue/work unit could be created and referenced, or a TODO comment with an explanatory description could be added.
	20	+* **A test should fail if an expected exception is not thrown.** Test libraries usually have methods to handle such cases. If the exception object must be examined, use a try-catch block that includes a fails() method at the end of the try block. Without the fails() method to make the test fail, the test would wrongfully pass if no exception were thrown:
	21	+
	22	+{{code}}
	23	+try {
	24	+ //code that should throw exception
	25	+ fails(); //executed when no exception was thrown
	26	+} catch (Exception e){
	27	+ //examine and assert exception
	28	+}
	29	+{{/code}}
	30	+
	31	+* **Different branches of production code should be checked in different tests.** Avoid if-statements in the test code, but at least be careful with assertions in if/if-else blocks, as the test may pass without executing them. To prevent this, add 'else {fails()}' at the end, or assert the condition and branch:
	32	+
	33	+{{code}}
	34	+// bad - still passes when x == false and y == false
	35	+if (x){
	36	+ //some logic
	37	+ assertTrue(y);
	38	+}
	39	+
	40	+// good - passes only if both conditions are met
	41	+if (x){
	42	+ //some logic
	43	+ assertTrue(y);
	44	+} else {
	45	+ fails()
	46	+}
	47	+
	48	+// also good
	49	+assertTrue(x);
	50	+//some logic
	51	+assertTrue(y);
	52	+{{/code}}