How to Review Acceptance Tests?

Common Testing Errors to Avoid

Importance of Attention to Detail in Test Implementation

• When reviewing tests implemented by colleagues or creating acceptance tests, it's crucial to focus on recurring specific errors that need avoidance.

• The scenario description must be rigorously implemented in the test steps, ensuring that the semantics and intent are accurately reflected in the implementation.

Aligning Implementation with Intent

• Each step's implementation should correspond precisely to its intended behavior; for instance, verifying if a user is on the student page requires specific commands.

• The last step in a sequence should effectively confirm whether the objective was achieved, while preceding steps prepare the system for this verification.

Eliminating Ambiguity

• It's essential to avoid ambiguity in similar steps; each description must map uniquely to an implementation.

• Adding extra details can help clarify steps and eliminate potential confusion when similar descriptions are used across different contexts.

Code Duplication Issues

• Avoid duplicating test code as a general best practice; instead of repeating commands, functions should invoke previously defined actions.

• This principle applies not only to regular code but also extends to automated testing scripts.

Cleaning Up After Tests

• If tests modify the environment (e.g., creating files or altering databases), it’s necessary to clean up afterward.

• For example, after uploading files during a test, ensure those files are deleted from their respective directories post-execution.

Ensuring Platform Independence

• Tests should function independently of platforms and languages; they must work across different operating systems and browsers without issues.

Testing Considerations for Language Configuration

Importance of Language Settings in Testing

• Emphasizes the need to ensure tests are run in browsers configured to the correct language, specifically English, to avoid issues.

• Suggests that instead of hardcoding specific text references in tests, it is better to use values associated with properties files for flexibility.

Utilizing Property Files

• Discusses using a properties file as a reference point for retrieving associated values during testing.