Scribd
Upload
233 views

TestNG - Assignment Problem Scenario & Instructions

1. The test scenario navigates to a URL and performs various actions like clicking elements and validating pages. 2. The test must be run on different browser and OS combinations using Selenium Grid on LambdaTest. 3. The submission requires running the tests on LambdaTest, submitting the code as a GitHub repo, and including logs, videos and screenshots in the test runs.

Uploaded by

MANISH KUMAR
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
233 views

TestNG - Assignment Problem Scenario & Instructions

1. The test scenario navigates to a URL and performs various actions like clicking elements and validating pages. 2. The test must be run on different browser and OS combinations using Selenium Grid on LambdaTest. 3. The submission requires running the tests on LambdaTest, submitting the code as a GitHub repo, and including logs, videos and screenshots in the test runs.

Uploaded by

MANISH KUMAR
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

TestNG: Assessment Problem

Test Scenario
1. Navigate to https://www.lambdatest.com/selenium-automation
2. Perform an explicit wait till the time all the elements in the DOM
are available.
3. Locate the WebElement CI/CD tools and click on the same.
4. Inside “CI/CD tools” click on the link titled “LEARN MORE”. Use the
right Selenium method to ensure that the link opens in a New Tab (and
not the Same Window).
5. Go to the tab where the link opened through “LEARN MORE” is
available
6. Verify whether the URL is the same as the expected URL (if not
throw an Assert)

7. On that page, first scroll to the bottom of the page and then to the
top of the page.
8. Close the current window and switch to the parent window (using
its window handle)
9. On the parent window, perform a click on the menu “Resources”.
Inside the “Resources” menu, click on the “Newsletter” option.
10. Search for the element “Let me read it first” using the CssSelector
property and click on the same.
11. Find “ALL EDITIONS'' on the page to confirm whether the
Newsletter page is open. If not, throw an assert and print the Stack
Trace.
12. If step (11) is successful, close the window and free the resources
held by the Selenium WebDriver.

Execution
The test scenario should be demonstrated on the following combinations of
browsers and platforms (using Selenium 4 Grid and Selenium 4 Java):

1. Chrome + 88.0 + Windows 10


2. MicrosoftEdge + 87.0 + macOS Sierra
3. Firefox + 82.0 + Windows 7
4. Internet Explorer + 11.0 + Windows 10

Important Notes
▪ Pass the browser and OS combinations to the test scenario from testng.xml
▪ Ensure that the functions in setup and teardown functions are not a part of
the @Test annotation. The TimeOut of the test duration should be set to 20
seconds. Parallelism should be at the Class Level (i.e. both the tests should
be executing in parallel on LambdaTest).
▪ Please ensure to use at least 3 different locators while performing the test.
▪ Please ensure that network logs, video recording, screenshots, and console
logs are enabled in all the test runs. Please refer to the Capability generator
for desired capabilities: https://www.lambdatest.com/capabilities-generator/
▪ Refer to the detailed instructions appended below for submission
guidelines.
Reference Images

Important Instructions
▪ You are required to submit the final solution within 36 hours of the
deadline. ▪ You must run the test on LambdaTest Cloud Selenium Grid in
parallel and mention the final Test ID(s) while submitting.
▪ You can submit the solution using Java programming language and TestNG
framework. We advise you to keep it as simple and as lean as possible. ▪
Please ensure that network logs, video recording, screenshots, and console
logs are enabled through the desired capabilities object while running the
test. You can refer to LambdaTest Capability Generator for the setting of
these desired capabilities.
▪ The final code needs to be submitted as a GitHub Repository. Please ensure
that it is a Private Repository shared with ‘LambdaTest-Certification’ or
[email protected]. You can refer to the Getting Started
Guide to get started with GitHub.
▪ While the code would be saved on Github, the final test run should be
initiated at Gitpod online IDE. You can refer to Getting Started with GitPod
to get started with Gitpod. To learn more about configuring your single
click Gitpod dev environment, refer here.
▪ You need to ensure that the GitHub repository is configured on Gitpod with
the required .gitpod.yml file. Please ensure that you attach a detailed
README.md file along with your GitHub repository. This should include
the instructions to run the test on the Gitpod dev environment.
▪ Setting up your LambdaTest account & running your first test
▪ Ensure that you register for your LambdaTest Account with the same email
address used to register for the certification and to appear for the
objective test. If you have not registered, you can register for a free
account from LambdaTest
Register. The free account comes with 15 days of automation trial access
that allows 100 minutes of automation testing.
▪ If you have used the automation minutes or have exceeded the allotted trail
access time, you can get a 24-hour trial access window by contacting
LambdaTest support. You can contact LambdaTest support from our
in-app
▪ chat support or by dropping a mail at [email protected] ▪ You can
also refer to our support docs to get started with Automation testing on the
LambdaTest platform.

You might also like