AI and test fixture generation

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-creators-ai-coding-AI-and-test-fixture-generation-r9a1-creators

1. What is a primary advantage of using AI to generate test fixtures?

   1. AI can produce large JSON arrays matching a specified schema
   2. AI can identify security vulnerabilities in your code
   3. AI can replace your entire test suite with one command
   4. AI can write test code that runs automatically

2. Which of the following is an example of an 'edge case' in test fixture generation?

   1. A test that passes on the first run
   2. A database connection that fails during fixture loading
   3. A user with an empty optional bio field
   4. A typical user with a standard username and email

3. When prompting an AI to generate test fixtures, what information should you always include?

   1. Your entire codebase
   2. The schema defining the data structure
   3. The names of your team members
   4. The database password

4. Why is it important to specify 'birthDate < createdAt' when generating user fixtures?

   1. Because the database will reject valid timestamps
   2. Because AI cannot generate dates
   3. Because JSON does not support dates
   4. Because fields must maintain logical relationships consistent with real-world rules

5. What limitation does AI have when generating test fixtures for your specific domain?

   1. AI cannot generate JSON
   2. AI always generates perfect code
   3. AI can read your mind without prompts
   4. AI cannot understand business rules that are obvious to domain experts

6. Why might generating 'real-looking' names and emails in test fixtures be problematic?

   1. Test fixtures cannot contain names
   2. They might accidentally match real people's actual PII
   3. The database will reject them
   4. JSON does not support text fields

7. What is the purpose of using email formats like 'test+1@example.com' in fixtures?

   1. To make the test run faster
   2. To ensure the email is obviously test data and not a real person's email
   3. To make the email look more realistic
   4. To bypass email validation

8. In the context of test fixtures, what is a 'schema'?

   1. A type of database
   2. A blueprint that defines the structure and types of data fields
   3. A testing framework
   4. A version control system

9. What should you explicitly tell AI to include in fixtures if you want to test how your code handles unusual input?

   1. Only data that will pass validation
   2. Edge cases like unicode characters, empty fields, and maximum-length values
   3. Only happy-path typical cases
   4. As few fixtures as possible

10. What does it mean that AI 'cannot generate truly random data with statistical properties'?

    1. AI cannot generate any random-looking data
    2. AI generates encrypted data
    3. AI may not produce realistic distributions (e.g., age clustering around certain demographics)
    4. AI always generates the same data

11. Why would you include 'unicode name' as a scenario when generating user fixtures?

    1. Unicode breaks all databases
    2. To ensure your application correctly handles international characters in names
    3. Unicode names are required by law
    4. Because AI cannot generate unicode

12. What is the benefit of including 'max-length fields' in your fixture scenarios?

    1. Shorter data is harder to generate
    2. AI cannot generate long text
    3. Maximum length fields do not exist
    4. It tests whether your application properly handles the longest allowed input without truncation or errors

13. When generating fixtures with created_at timestamps, why specify both 'recent' and 'old' timestamps?

    1. Timestamps must always be the same age
    2. Because databases reject mid-aged timestamps
    3. Because AI cannot generate current timestamps
    4. To test time-sensitive features like 'users active in the last 30 days' or cache expiration

14. How should your fixture scenarios handle optional fields?

    1. Always provide a default value
    2. Always leave them empty
    3. Remove optional fields from the schema
    4. Include both fixtures with values and fixtures where they are null or empty

15. A developer asks AI to generate fixtures for an online store. AI produces typical orders but misses the scenario where a customer orders zero items. Why did this happen?

    1. AI always generates perfect data
    2. The developer did not explicitly mention this domain-specific edge case
    3. AI cannot generate JSON
    4. Online stores never allow zero-item orders