Test Strategy & Plan This document specifies both test strategy and planning used to test the Challenging DOM application.
- Introduction and Scope: ➢ The purpose of the challenging DOM app is to show how can we use different locators such as id, name, xpath, css-selector etc. to find the same element on a webpage. ➢ Both static and dynamic locators are present in the challenging DOM application. ➢ The scope of this project is to test the basic functionality of application by uniquely identify both static and dynamic elements using advance locator techniques. • Test automation is used to automate the functionality. 2.2 Environment Specifications: • Windows 10 laptop. • Chrome browser version 84
- Testing tools: List outs various tool used for testing challenging-DOM. • Selenium WebDriver: Web automation tool. • SpecFlow: C# Selenium Test • Visual Studio 2022: IDE • SpecFlow frameWork with Nunit and .Net6.0 • Core Java: To write test scripts
- Test items: ➢ There are three buttons on webpage that execute a functionality on clicking. The locator (eg. id) of these buttons are dynamic in nature. It changes when we click either of the three buttons. ➢ The name on each of the buttons also change every time we click it.
- Features to be tested:
- Verify if the name of the application - Challenging DOM is displayed on page.
- Identify dynamic locators of three buttons using dynamic xpath.
- Verify if all three buttons are enabled.
- Verify clicking of three buttons using dynamic xpath.
- Test Execution: To run automation scripts: ➢ Set up the environment using tools described in section 3. ➢ In project, Test Explorer > Run > ChallengeDOM Suite.
- Test Deliverables ➢ Test strategy and plan document. ➢ Test scenarios ➢ Test scripts (Location in project folder: ChallengeDom/StepDefinitions/