Testing in the software development lifecycle in Testing Fundamentals - Test Execution Trace

Test Overview

This test simulates a simple verification of a login page during the software development lifecycle. It checks that the login button is present and clickable, and that a successful login message appears after submitting valid credentials.

Test Code - Selenium with unittest

Testing Fundamentals

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import unittest

class TestLoginPage(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://example.com/login')

    def test_login_button_and_success_message(self):
        driver = self.driver
        wait = WebDriverWait(driver, 10)

        # Wait for login button to be clickable
        login_button = wait.until(EC.element_to_be_clickable((By.ID, 'login-btn')))
        self.assertTrue(login_button.is_displayed())

        # Enter username and password
        driver.find_element(By.ID, 'username').send_keys('testuser')
        driver.find_element(By.ID, 'password').send_keys('password123')

        # Click login button
        login_button.click()

        # Wait for success message
        success_message = wait.until(EC.visibility_of_element_located((By.ID, 'success-msg')))
        self.assertEqual(success_message.text, 'Login successful!')

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts and opens Chrome browser	Browser window opens at 'https://example.com/login' page	—	PASS
2	Waits until the login button with ID 'login-btn' is clickable	Login page fully loaded with login button visible and enabled	Checks that login button is displayed	PASS
3	Finds username and password input fields and enters credentials	Username field contains 'testuser', password field contains 'password123'	—	PASS
4	Clicks the login button	Login form submitted, page processes login	—	PASS
5	Waits for the success message with ID 'success-msg' to appear	Success message 'Login successful!' is visible on the page	Verifies success message text equals 'Login successful!'	PASS
6	Test ends and browser closes	Browser window closes	—	PASS

Failure Scenario

Failing Condition: Login button with ID 'login-btn' is not found or not clickable within 10 seconds

Execution Trace Quiz - 3 Questions

What does the test verify first after opening the login page?

A That the login button is clickable

B That the success message is visible

C That the username field is empty

D That the password is correct

Key Result

Always wait explicitly for elements to be ready before interacting with them to avoid flaky tests during software development lifecycle.

Practice

1. Which phase in the software development lifecycle is primarily responsible for planning how testing will be done?

easy

A. Deployment

B. Coding

C. Requirement Analysis

D. Maintenance

Solution

1. Step 1: Understand the role of Requirement Analysis

   This phase gathers and analyzes what the software should do, including defining test requirements.

2. Step 2: Identify testing planning activities

   Planning how to test is done early, during Requirement Analysis, to ensure tests cover all needs.

3. Final Answer:

   Requirement Analysis -> Option C

4. Quick Check:

   Testing plan starts in Requirement Analysis [OK]

Hint: Testing plans start with requirements, not coding [OK]

Common Mistakes:

• Confusing coding phase with testing planning
• Thinking deployment includes test planning
• Assuming maintenance is for initial test planning

2. Which of the following is the correct syntax to describe a test case in a test plan document?

easy

A. Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully

B. Test Case: Verify login\nResult: Success\nID: 001

C. ID: 001\nTest: Login check\nOutcome: Pass

D. Case Test 1\nCheck login\nExpected: true

Solution

1. Step 1: Identify standard test case format

   Standard test cases include clear ID, description, and expected result fields.

2. Step 2: Compare options to standard format

   Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully matches the clear, structured format; others are incomplete or unclear.

3. Final Answer:

   Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully -> Option A

4. Quick Check:

   Clear ID, description, expected result = Test Case ID: TC001\nDescription: Verify login functionality\nExpected Result: User logs in successfully [OK]

Hint: Look for clear ID, description, expected result format [OK]

Common Mistakes:

• Using unclear or incomplete test case fields
• Mixing field names or order
• Omitting expected results

3. Consider this code snippet representing a simple test function in Python:

def test_addition():
    result = 2 + 3
    assert result == 5
    print('Test passed')

What will be the output when this test runs?

medium

A. SyntaxError

B. Test passed

C. No output

D. AssertionError

Solution

1. Step 1: Analyze the test function logic

   The function adds 2 + 3, stores 5 in result, then asserts result equals 5, which is true.

2. Step 2: Determine output after assertion

   Since assertion passes, the print statement runs, outputting 'Test passed'.

3. Final Answer:

   Test passed -> Option B

4. Quick Check:

   Assertion true means print runs [OK]

Hint: If assert condition is true, print runs [OK]

Common Mistakes:

• Thinking assertion always raises error
• Expecting no output from print
• Confusing syntax with runtime error

4. A tester wrote this test script snippet:

def test_divide():
    result = 10 / 0
    assert result == 0

What is the main problem with this test?

medium

A. Test function name is incorrect

B. Assertion should check for 10, not 0

C. Missing print statement

D. Division by zero causes runtime error

Solution

1. Step 1: Identify the operation causing error

   Dividing 10 by 0 causes a ZeroDivisionError at runtime.

2. Step 2: Understand impact on test execution

   Because of the error, assertion is never reached and test fails with exception.

3. Final Answer:

   Division by zero causes runtime error -> Option D

4. Quick Check:

   Division by zero = runtime error [OK]

Hint: Division by zero always causes error [OK]

Common Mistakes:

• Ignoring runtime error and focusing on assertion
• Thinking assertion is wrong instead
• Assuming print statement needed

5. In a software project, testing is integrated throughout the lifecycle. Which testing type is best suited to catch issues caused by changes in code after deployment?

hard

A. Regression Testing

B. Unit Testing

C. Acceptance Testing

D. Smoke Testing

Solution

1. Step 1: Understand testing types and their purpose

   Unit Testing checks small code parts; Acceptance Testing checks user needs; Smoke Testing checks basic functionality.

2. Step 2: Identify testing for post-deployment changes

   Regression Testing reruns tests to ensure new changes don't break existing features after deployment.

3. Final Answer:

   Regression Testing -> Option A

4. Quick Check:

   Regression Testing catches post-change issues [OK]

Hint: Regression Testing checks after code changes [OK]

Common Mistakes:

• Confusing unit testing with regression testing
• Thinking acceptance testing covers code changes
• Assuming smoke testing is for detailed checks