What are common pitfalls or gotchas with test discovery (prove)?

When using Perl's test discovery tool, commonly known as prove, there are several pitfalls and gotchas that users may encounter. Being aware of these can help streamline the testing process and avoid unnecessary errors.

Common Pitfalls with Test Discovery (prove)

• Incorrect Test File Naming: prove relies on specific naming conventions for test files. Ensure your test files are named as t/*.t to be correctly identified.
• Test Suite Structure: Improper directory structures can lead to tests not being found; maintain a standard hierarchy for better results.
• Skipping Test Cleanup: Failing to clean up after tests can lead to false positives in subsequent runs. Always ensure that your tests leave no residual effects.
• Ignoring Test Dependencies: If your tests rely on certain modules or files, ensure they are accessible in your test environment.
• Overlooking Exit Codes: The test result codes from prove may indicate failures, but misinterpretation may lead to overlooking important failures.

By keeping these common issues in mind, you can improve your experience with test discovery in Perl.