Development Processes: SDLC, retro, code freeze

Quiz: SDLC, retrospective, code freeze, acceptance criteria, sprint planning, test environments, CI and a bug on production.

Question 1 of 8Correct: 0Incorrect: 0

Questions and explanations

Find an explanation for each question here. To test yourself, take the quiz above first.

  1. What is SDLC and why should QA know its stages?

    SDLC (Software Development Life Cycle) describes the product’s path from an idea to maintenance. A tester takes part not only at the testing stage, but also in working with requirements and the release.

  2. At a retrospective everyone complains that testing is constantly pushed to the last day of the sprint. How should QA use the retro?

    A retro works when the problem is stated through facts, not as an accusation, and ends with a concrete action with an owner and a deadline. This way the team changes the process rather than just complaining.

  3. What is a code freeze before a release?

    A code freeze reduces the risk that late changes break what has already been checked. During this time QA usually runs the final regression and confirms that the build can be released.

  4. What are acceptance criteria in a user story and why are they important for QA?

    Acceptance criteria turn a general task into verifiable conditions. If they are missing or vague, they should be clarified before development starts.

  5. What happens at sprint planning and what is the role of QA?

    At planning the team decides what it can realistically complete in the sprint. Testing is part of the effort, so QA’s participation helps avoid overloading the sprint and reveals unclear requirements in advance.

  6. Where does a tester usually check new functionality?

    The test environment is close to production but contains test data. Checks on production are done carefully and only when agreed (for example, a quick smoke test after a release).

  7. What is CI (continuous integration) in general terms?

    CI (continuous integration) quickly shows that a change broke the build or the tests while it is still fresh in the author’s mind. For QA it is also a way to see which automated tests passed for each build.

  8. You found a critical bug already on production. What do you do first?

    For critical bugs, speed of information matters. After a hotfix, the fix should be verified and regression checks of the affected areas performed.