Tester mindset and thinking in Testing Fundamentals - Test Execution Trace

Test Overview

This test simulates a tester approaching a simple login form to verify if the login button is enabled only when both username and password fields are filled. It checks the tester's mindset of exploring positive and negative scenarios.

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 TestLoginButton(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://example.com/login')

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

        username = wait.until(EC.presence_of_element_located((By.ID, 'username')))
        password = wait.until(EC.presence_of_element_located((By.ID, 'password')))
        login_button = wait.until(EC.presence_of_element_located((By.ID, 'login-btn')))

        # Initially, login button should be disabled
        self.assertFalse(login_button.is_enabled(), 'Login button should be disabled initially')

        # Enter username only
        username.send_keys('user1')
        self.assertFalse(login_button.is_enabled(), 'Login button should remain disabled with only username')

        # Enter password
        password.send_keys('pass1')
        self.assertTrue(login_button.is_enabled(), 'Login button should be enabled when both fields are filled')

    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 browser opens Chrome	Chrome browser window opens and navigates to https://example.com/login	—	PASS
2	Waits until username input field is present	Login page loaded with username, password fields and login button visible	Username field is present	PASS
3	Checks that login button is initially disabled	Login button is visible but disabled	Assert login button is not enabled	PASS
4	Enters 'user1' into username field	Username field contains 'user1', password field empty, login button still disabled	Assert login button remains disabled	PASS
5	Enters 'pass1' into password field	Both username and password fields filled, login button enabled	Assert login button is enabled	PASS
6	Test ends and browser closes	Browser window closes	—	PASS

Failure Scenario

Failing Condition: Login button remains disabled even after both username and password are entered

Execution Trace Quiz - 3 Questions

What does the test verify about the login button initially?

A It is disabled before any input

B It is enabled before any input

C It is hidden before any input

D It is clickable before any input

Key Result

A good tester thinks about different input combinations and verifies UI behavior for each, including initial states and changes after user actions.

Practice

1. What is the main goal of having a tester mindset?

easy

A. To manage the project timeline

B. To write code faster than developers

C. To design the software architecture

D. To think like a user and find problems in the software

Solution

1. Step 1: Understand the tester mindset purpose

   The tester mindset focuses on thinking like a user and looking for bugs or issues.

2. Step 2: Compare options with this purpose

   Only To think like a user and find problems in the software matches this goal; others relate to coding, design, or management, not testing mindset.

3. Final Answer:

   To think like a user and find problems in the software -> Option D

4. Quick Check:

   Tester mindset = find problems like a user [OK]

Hint: Tester mindset = think like user, find bugs fast [OK]

Common Mistakes:

• Confusing tester mindset with coding skills
• Thinking tester mindset is about project management
• Assuming tester mindset means designing software

2. Which of the following is the correct way to write a test case title?

easy

A. Test login with valid username and password

B. loginTest123

C. Check if login works

D. TestCase1

Solution

1. Step 1: Identify clear and descriptive test case titles

   A good test case title clearly describes what is tested, like Test login with valid username and password.

2. Step 2: Evaluate other options for clarity

   The other options are vague or use unclear naming, not best practice.

3. Final Answer:

   Test login with valid username and password -> Option A

4. Quick Check:

   Clear descriptive title = Test login with valid username and password [OK]

Hint: Test case title should clearly describe the test [OK]

Common Mistakes:

• Using vague or generic titles
• Including technical jargon in titles
• Using non-descriptive codes or numbers

3. Consider this test scenario: A user tries to submit a form with an empty required field. What should the tester expect?

medium

A. An error message appears asking to fill the required field.

B. The page reloads without any message.

C. The form submits successfully without errors.

D. The form clears all entered data automatically.

Solution

1. Step 1: Understand form validation rules

   Required fields must be filled; empty submission should trigger an error.

2. Step 2: Match expected behavior with options

   Only An error message appears asking to fill the required field. describes the correct behavior: showing an error message.

3. Final Answer:

   An error message appears asking to fill the required field. -> Option A

4. Quick Check:

   Empty required field = error message [OK]

Hint: Empty required field triggers error message [OK]

Common Mistakes:

• Expecting form to submit without validation
• Assuming page reloads silently
• Thinking form clears data automatically

4. You wrote a test case but it always passes even when the feature is broken. What is the most likely problem?

medium

A. The feature is actually working fine.

B. The test case is missing assertions to check results.

C. The test environment is down.

D. The test case has too many steps.

Solution

1. Step 1: Analyze why test always passes despite broken feature

   If a test passes wrongly, it likely lacks proper checks (assertions).

2. Step 2: Evaluate other options

   Feature broken means B is false; environment down or too many steps don't cause false passes.

3. Final Answer:

   The test case is missing assertions to check results. -> Option B

4. Quick Check:

   Missing assertions cause false passes [OK]

Hint: Always include assertions to verify expected results [OK]

Common Mistakes:

• Assuming feature is fine without checking
• Ignoring missing assertions
• Blaming environment without evidence

5. You want to test a login form thoroughly. Which approach best shows a tester mindset?

hard

A. Test only the UI layout without entering data.

B. Test only valid username and password combinations.

C. Test valid, invalid, empty, and boundary inputs to find issues.

D. Test by asking developers if the form works.

Solution

1. Step 1: Understand thorough testing from tester mindset

   Tester mindset means being curious and testing many scenarios, including edge cases.

2. Step 2: Compare options for coverage

   Test valid, invalid, empty, and boundary inputs to find issues. covers valid, invalid, empty, and boundary inputs, showing thoroughness.

3. Final Answer:

   Test valid, invalid, empty, and boundary inputs to find issues. -> Option C

4. Quick Check:

   Test many scenarios = Test valid, invalid, empty, and boundary inputs to find issues. [OK]

Hint: Test many input types, not just happy paths [OK]

Common Mistakes:

• Testing only valid inputs
• Ignoring boundary or empty inputs
• Relying on developers' word only