Test environment setup in Testing Fundamentals - Build an Automation Script

Verify test environment setup for web application testing

Preconditions (3)

Step 1: Open the test automation tool

Step 2: Launch the web browser using the automation tool

Step 3: Navigate to the test application URL 'https://example.com/login'

Step 4: Verify the login page loads successfully by checking the page title is 'Login - ExampleApp'

Step 5: Close the browser

✅ Expected Result: The login page loads successfully with the correct title, confirming the test environment is set up correctly

Automation Requirements - Selenium WebDriver with Python

Assertions Needed:

Verify browser launches successfully

Verify page title matches 'Login - ExampleApp'

Verify browser closes without errors

Best Practices:

Use explicit waits to wait for page load

Use proper locators for elements

Handle browser setup and teardown in setup and teardown methods

Keep test code clean and readable

Automated Solution

Testing Fundamentals

import unittest
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

class TestEnvironmentSetup(unittest.TestCase):
    def setUp(self):
        # Setup Chrome WebDriver
        self.driver = webdriver.Chrome()
        self.driver.maximize_window()

    def test_login_page_loads(self):
        driver = self.driver
        driver.get('https://example.com/login')

        # Wait until the title is as expected
        WebDriverWait(driver, 10).until(EC.title_is('Login - ExampleApp'))

        # Assert the page title
        self.assertEqual(driver.title, 'Login - ExampleApp')

    def tearDown(self):
        # Close the browser
        self.driver.quit()

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

This test script uses Python's unittest framework with Selenium WebDriver.

setUp() method initializes the Chrome browser and maximizes the window to ensure consistent view.

The test test_login_page_loads navigates to the login page URL and waits explicitly for the page title to be 'Login - ExampleApp' to confirm the page loaded correctly.

It then asserts the page title to verify the correct page is displayed.

The tearDown() method closes the browser to clean up after the test.

Explicit waits are used to avoid timing issues, and the code is structured for clarity and maintainability.

Common Mistakes - 3 Pitfalls

{'mistake': 'Using time.sleep() instead of explicit waits', 'why_bad': 'It causes unnecessary delays or flaky tests if the page loads faster or slower than the sleep time.', 'correct_approach': "Use Selenium's explicit waits like WebDriverWait with expected conditions to wait only as long as needed."}

Not closing the browser after test

Hardcoding element locators without validation

Bonus Challenge

Now add data-driven testing to verify the login page loads for three different URLs (e.g., staging, production, and test environment URLs).

Show Hint

Practice

1. What is the main purpose of setting up a test environment in software testing?

easy

A. To create a safe space to test software without affecting real users

B. To deploy the software directly to all users

C. To write the software code faster

D. To replace the production environment permanently

Solution

1. Step 1: Understand the role of a test environment

   A test environment is a setup where software can be tested safely without impacting real users or live data.

2. Step 2: Compare options with the purpose

   Only To create a safe space to test software without affecting real users describes creating a safe space for testing without affecting real users, which is the main goal.

3. Final Answer:

   To create a safe space to test software without affecting real users -> Option A

4. Quick Check:

   Test environment purpose = safe testing space [OK]

Hint: Test environment protects real users during testing [OK]

Common Mistakes:

• Confusing test environment with production
• Thinking test environment is for faster coding
• Assuming test environment replaces production

2. Which of the following is the correct way to describe a test environment setup?

easy

A. Installing and configuring hardware and software similar to production

B. Writing test cases without any software or hardware

C. Deploying software directly to users without testing

D. Using only cloud services without any local setup

Solution

1. Step 1: Identify what test environment setup involves

   It includes installing and configuring hardware and software that mimic the production environment.

2. Step 2: Evaluate each option

   Installing and configuring hardware and software similar to production correctly describes the setup process. Others describe unrelated or incorrect actions.

3. Final Answer:

   Installing and configuring hardware and software similar to production -> Option A

4. Quick Check:

   Setup = install + configure like production [OK]

Hint: Setup means install and configure like production [OK]

Common Mistakes:

• Confusing test environment with writing test cases
• Skipping hardware setup
• Thinking deployment equals testing

3. Consider this code snippet for setting up a test environment configuration file:

config = {
  'database': 'test_db',
  'server': 'localhost',
  'debug_mode': True
}

if config['debug_mode']:
  print('Debugging is enabled')
else:
  print('Debugging is disabled')

What will be the output when this code runs?

medium

A. Debugging is disabled

B. Debugging is enabled

C. KeyError: 'debug_mode'

D. SyntaxError

Solution

1. Step 1: Check the value of 'debug_mode' in config

   The key 'debug_mode' exists and is set to True.

2. Step 2: Evaluate the if condition

   Since 'debug_mode' is True, the code prints 'Debugging is enabled'.

3. Final Answer:

   Debugging is enabled -> Option B

4. Quick Check:

   debug_mode = True -> prints enabled [OK]

Hint: Check boolean value to predict print output [OK]

Common Mistakes:

• Assuming debug_mode is False by default
• Expecting a KeyError for existing key
• Confusing syntax error with logic

4. You have this test environment setup code snippet:

def setup_env():
  env = {}
  env['db'] = 'test_db'
  env['server'] = 'localhost'
  return env

config = setup_env()
print(config['database'])

What error will occur when running this code?

medium

A. NameError: setup_env not defined

B. TypeError: unsupported operand

C. KeyError: 'database'

D. No error, prints 'test_db'

Solution

1. Step 1: Analyze the keys set in env dictionary

   The dictionary has keys 'db' and 'server', but not 'database'.

2. Step 2: Check the print statement key access

   Accessing config['database'] causes a KeyError because 'database' key does not exist.

3. Final Answer:

   KeyError: 'database' -> Option C

4. Quick Check:

   Access missing key -> KeyError [OK]

Hint: Match dictionary keys exactly to avoid KeyError [OK]

Common Mistakes:

• Assuming 'db' and 'database' are the same key
• Expecting no error on missing key
• Confusing KeyError with NameError

5. You want to create a test environment that closely mimics production but avoids affecting live data. Which combination of actions is best to achieve this?

hard

A. Skip environment setup and test directly in production during off-hours

B. Use the production database directly but disable user access

C. Test on a developer's local machine with random data only

D. Use a separate database with production-like data and configure identical software versions

Solution

1. Step 1: Identify key requirements for test environment

   It should mimic production closely and avoid affecting live data.

2. Step 2: Evaluate each option against these requirements

   Use a separate database with production-like data and configure identical software versions uses a separate database with similar data and matching software versions, fulfilling both needs. Others risk affecting live data or lack similarity.

3. Final Answer:

   Use a separate database with production-like data and configure identical software versions -> Option D

4. Quick Check:

   Separate but similar environment = safe, reliable testing [OK]

Hint: Separate but similar environment ensures safe testing [OK]

Common Mistakes:

• Testing directly on production risks data loss
• Using random data lacks production similarity
• Disabling user access doesn't protect data integrity