Automated Testing Guidelines FAQs

Question 1

Does this skill help with test isolation?

Accepted Answer

Yes, it provides technical patterns for using temporary directories and cleanup hooks (like afterEach) to ensure that every test runs independently without side effects.

Question 2

How are external network calls handled in tests?

Accepted Answer

The guidelines strictly mandate mocking third-party network services. Tests must use fixtures captured from real API responses that have been scrubbed of all PII (Personally Identifiable Information).

Question 3

What counts as a 'user entry point' for testing?

Accepted Answer

User entry points include CLI commands, API endpoints, and exported public functions. The guidelines require at least one basic happy-path test for every entry point to prove it works.

Question 4

Why does this skill prefer integration tests over unit tests?

Accepted Answer

Integration tests validate the public interface and actual behavior. This ensures that if you refactor internal implementation details but the output remains correct, your tests won't break unnecessarily.

Question 5

What is a regression test in this context?

Accepted Answer

A regression test is a test specifically designed to catch a previously identified bug. It must fail before the fix is applied and pass afterward to ensure the bug never returns.

Automated Testing Guidelines

Key Features

Use Cases

Automated Testing Guidelines

Key Features

Use Cases