Uploading Excel Test Templates

This Page Describes on how to download sample document and fill in the datas.

After downloading the sample documents, users should follow the instructions below to accurately fill in the test data required for Functional Testing.

To upload a test document, follow these steps:

1. Click the Documents icon form the menu bar

2. On the Documents Page, select the icon labeled Download Button. This action will trigger a dropdown menu, allowing you to download sample Testcase sheets.

1. Authentication.xls

Download the Authentication.xls file from the dropdown, which contains sample test data for Google search. Users can modify the data sheet according to their specific use cases. The Authentication.xls file comprises three sheets: AboutMe, DataPool, and TestScriptDataPool. The AboutMe sheet provides comprehensive instructions on populating the DataPool and TestScriptDataPool sheets. In the DataPool sheet, users are required to input the URLs for each environment they intend to test.

Usecase for DataPool Sheet

1. It is mandatory that the Starting Tag and Ending Tag names match.

2. The Header Name must remain unchanged and should not be replaced.

3. Users are required to input application URLs for all four environments.

4. The Requirement column should only contain Dev, Test, UAT, Prod. Values must not be replaced.

2. UIProperties.xls

Download the UIProperties file, containing sample test data for Google search. Users can modify the data sheet according to their specific use cases. The UIProperties file includes an AboutUs sheet, providing detailed instructions on populating the UIProperties sheet. Users have the option to create a new sheet name and add properties to it.

Usecase for UIProperty sheet

1. Users should create a new sheet with a name that contains no spaces.

2. The starting and ending tags should have the same name.

3. Headers include name, type, value, action, id, description, expectedresult, pass_actualresult, and fail_actualresult.

4. The Name column should contain the step or action name.

5. The Type column indicates the type of CSS element properties (e.g., Id, Name, xpath).

6. The Value column should be filled with corresponding type values (e.g., for css locator=Id, value=“firstName”).

7. The Action column should contain the Selenium action to be performed.

8. The ID column should be filled with the ID value.

9. The Description column should provide a brief note on the test case.

10. The ExpectedResult column should specify the expected result after executing the test case.

11. The PassActualResult column should describe the outcome of a passed test case.

12. The FailActualResult column should describe the outcome of a failed test case.

3. Test Scenario

After completing the UIProperties sheet, users should populate the test scenario data in the TestScriptDataPool sheet within the Authentication.xls file.

Usecase for TestScriptDataPool Sheet

1. It is mandatory that the Starting Tag and End Tag names match.

2. The Header Name must remain unchanged and should not be replaced.

3. The DataRow column should always start with the vlaue 2.

4. The PropertySheetName should match the name declared by the user in their UIProperties Sheet Name.

5. The Data_TableName represents the module name declared by the user in their UserData Sheet and the Data_TableName should be unique.

6. The OpenBrowser and CloseBrowser columns should only contain Y or N values to indicate whether to open/close the browser.

7. The Run column indicates whether the user intends to run this module or not.

4. User Data

Upon completion of the Test Scenario data, download the UserData file, which includes sample test data for Google search. Users can modify the sample sheet according to their needs. It comprises the TestData values corresponding to the UIProperties listed in the UIProperties sheet.

Usecase for TestScriptDataPool Sheet

1. It is essential that Columns A & D only contain values corresponding to data_tablename as declared in the Authentication.xls TestScriptDataPool sheet. These values represent the start and end tag names, each representing a module.

2. The TestDetails Tag will be present by default at the beginning.

3. Column B denotes the field, while C signifies their corresponding values.

4. TestStep, TestcaseDescription, Requirement, TestModule are mandatory rows in Column B. Their values must be entered in Column C for every declared tag. Additionally, users are required to input data for the UIProperties.xls Name column and their corresponding values in Column C.

5. Additional test cases can be added by inputting values in Column D.