Choose the phase in the software development lifecycle when integration testing is usually done.
Integration testing checks how different parts work together, so it happens after individual parts are tested.
Integration testing is done after unit testing to verify that combined components work together correctly, but before system testing which tests the whole system.
Given the following test execution summary, what is the total number of failed tests?
Test Suite: User Login Tests Tests run: 10 Tests passed: 8 Tests failed: 2 Tests skipped: 0
Look for the line that says 'Tests failed'.
The summary clearly states 'Tests failed: 2', so the number of failed tests is 2.
Choose the assertion statement that correctly checks if the function get_items() returns a list with at least one item.
def get_items(): return ['apple', 'banana']
Think about how to check the size of a list.
Checking that the length of the list is greater than zero confirms it is not empty. Other options check for empty or None values incorrectly.
What error will this test code raise when executed?
def test_divide(): result = divide(10, 0) assert result == 0
Check if the function used is defined anywhere.
The code calls 'divide' which is not defined, so Python raises a NameError before any assertion or division happens.
Choose the testing stage that is best suited to run right after a developer commits code to the repository in a Continuous Integration/Continuous Deployment (CI/CD) pipeline.
Think about fast, automated tests that check small pieces of code.
Unit tests run quickly and verify individual components immediately after code changes, helping catch errors early in CI/CD pipelines.