In traditional Waterfall projects, testing usually happens after development is complete. How does Agile change this timing?
Think about how Agile breaks work into small parts called iterations or sprints.
Agile promotes continuous testing alongside development in short cycles, allowing faster feedback and early bug detection.
Choose the statement that best reflects how testers work in Agile teams.
Consider Agile values of collaboration and communication.
In Agile, testers are part of the team and work closely with developers and product owners to ensure quality continuously.
Given the following Python test automation code snippet simulating Agile continuous testing, what will be printed?
def run_tests(tests): passed = 0 for test in tests: if test(): passed += 1 return f"{passed} of {len(tests)} tests passed" def test_feature_a(): return True def test_feature_b(): return False test_results = run_tests([test_feature_a, test_feature_b]) print(test_results)
Count how many test functions return True.
Only test_feature_a returns True, so 1 of 2 tests passed.
A team following Agile skips writing automated tests for new features to save time. What is the main risk of this practice?
Think about how automation supports fast feedback in Agile.
Skipping automation risks missing bugs and slows down future testing, harming Agile's fast delivery goals.
Choose the testing framework commonly used in Agile to write tests in natural language that describe expected behavior.
Look for the framework that uses 'Given-When-Then' syntax.
Cucumber supports BDD by allowing tests to be written in plain language, improving communication among team members.