Best Practices

In any of the levels of testing explained before it is necessary to follow some basic good practices in order to get a good test case. The test cases must be clear, concise, and complete. Furthermore, it is important that test cases must be simple and specific, but these are only a few characterizes in a test case. The idea is to show that designing, conceptualizing, and writing a test case is as important as writing any other method into the code.

The following are some good practices necessary in the company:

• The test case must have a descriptive name.

• It must be atomic: only one scenario must be checked and must not have dependencies with other test cases.

• The test case must be simple and specific for any person to understand the test without any help from the author.

• It must not be redundant with other test cases.

• The test case must avoid unnecessary steps.

• If it is necessary, add methods to “Initialize” and “Clean” the test case in a level of test, class, or assembly depending on the context.

• The test case must be reliable.

• The test case must be validated to avoid bad responses or false positives.

• Finally, the test case must be assured the quality expected.

In order to read more good practices, see References about good practices.