Testing interview questions
API Contract Testing, Arrange Act Assert, Basic pytest Assertions, Boundary And Failure Tests, Fixtures, Monkeypatching and Mocks
225 questions with answers and explanations · 207 flashcards
Questions (page 4 of 5)
- If you wrote a test around reliability stories, what should the test prove first?Multiple choiceHard
- If you wrote a test around tmp_path and file tests, what should the test prove first?Multiple choiceHard
- What does a strong engineer do when reasoning through monkeypatching and mocks code?Multiple choiceMedium
- Which option treats monkeypatching and mocks as an engineering policy decision instead of a syntax trick?Multiple choiceHard
- What does a strong engineer do when reasoning through fixtures code?Multiple choiceMedium
- You cannot rewrite everything today. What is the best incremental improvement around fixtures?Multiple choiceMedium
- Which boundary choice best fits tmp_path and file tests in a maintainable Python system?Multiple choiceHard
- Which judgment is strongest when choosing a data shape for reliability stories?Multiple choiceHard
- A senior interviewer asks for one tradeoff behind monkeypatching and mocks. What is the strongest follow-up?Multiple choiceHard
- You cannot rewrite everything today. What is the best incremental improvement around monkeypatching and mocks?Multiple choiceMedium
- What is the healthiest performance judgment around tmp_path and file tests?Multiple choiceHard
- What assumption should be made explicit when working with parameterized tests?Multiple choiceMedium
- When is parameterized tests being used in the wrong way?Multiple choiceMedium
- What is the clearest sign that code around fixtures should be refactored?Multiple choiceMedium
- What is the clearest sign that code around parameterized tests should be refactored?Multiple choiceMedium
- When is tmp_path and file tests being used in the wrong way?Multiple choiceHard
- When is reliability stories being used in the wrong way?Multiple choiceHard
- A teammate submits shaky monkeypatching and mocks code. Which review comment is the strongest?Multiple choiceMedium
- Another engineer will maintain this code later. What choice helps the most around monkeypatching and mocks?Multiple choiceMedium
- What kind of contract clarity matters most for monkeypatching and mocks?Multiple choiceHard
- What kind of contract clarity matters most for reliability stories?Multiple choiceHard
- Which boundary choice best fits fixtures in a maintainable Python system?Multiple choiceMedium
- What assumption should be made explicit when working with monkeypatching and mocks?Multiple choiceMedium
- Which explanation would sound strongest in an interview when discussing tmp_path and file tests?Multiple choiceHard
- Which response shows the healthiest evidence-first mindset around reliability stories?Multiple choiceHard
- Which option treats parameterized tests as an engineering policy decision instead of a syntax trick?Multiple choiceHard
- A teammate submits shaky reliability stories code. Which review comment is the strongest?Multiple choiceHard
- Which response shows the healthiest evidence-first mindset around parameterized tests?Multiple choiceHard
- What do interviewers usually hear as a strong signal when you discuss tmp_path and file tests well?Multiple choiceHard
- What is the clearest sign that code around monkeypatching and mocks should be refactored?Multiple choiceMedium
- Another engineer will maintain this code later. What choice helps the most around tmp_path and file tests?Multiple choiceHard
- Which option is the safer default when shipping code around monkeypatching and mocks?Multiple choiceHard
- Which option describes the most likely pitfall around reliability stories?Multiple choiceHard
- A bug appears around reliability stories. What is the strongest first debugging move?Multiple choiceHard
- What assumption should be made explicit when working with fixtures?Multiple choiceMedium
- What kind of contract clarity matters most for parameterized tests?Multiple choiceHard
- What do interviewers usually hear as a strong signal when you discuss parameterized tests well?Multiple choiceHard
- A senior interviewer asks for one tradeoff behind reliability stories. What is the strongest follow-up?Multiple choiceHard
- Which explanation would best help the team align on reliability stories?Multiple choiceHard
- A teammate submits shaky parameterized tests code. Which review comment is the strongest?Multiple choiceMedium
- Which judgment is strongest when choosing a data shape for parameterized tests?Multiple choiceMedium
- Which option is the safer default when shipping code around tmp_path and file tests?Multiple choiceHard
- What is the healthiest performance judgment around fixtures?Multiple choiceMedium
- Which response shows the healthiest evidence-first mindset around tmp_path and file tests?Multiple choiceHard
- Which boundary choice best fits monkeypatching and mocks in a maintainable Python system?Multiple choiceMedium
- Which explanation would best help the team align on fixtures?Multiple choiceMedium
- Which boundary choice best fits parameterized tests in a maintainable Python system?Multiple choiceMedium
- If monkeypatching and mocks fails in production, what handling philosophy is strongest?Multiple choiceMedium
- What does a strong engineer do when reasoning through parameterized tests code?Multiple choiceMedium
- What is the healthiest performance judgment around reliability stories?Multiple choiceHard