My Certificate Find a Certificate About Certification QA Terminology Basics of Software Testing Basics of Test Automation QA Processes Overview Basics of testRigor BDD & SDD Web Testing Overview Mobile Testing Overview Native Desktop App Testing Overview API Testing Overview Click / Drag / Hover Entering Data Variables Validations Scrolls and Swipes Dealing with Dates and Times Dealing with Emails Working with Tables Conditional Sequences Cycles & Loops Reusable Rules SMS and Phone Calls Managing Multiple Environments Settings Integrations AI and Prompt Engineering Final Exam

Generative AI-Based Testing Certification

Final Exam

Final Exam

Test your knowledge

Instructions: Select the correct answer(s) to each question. If you refresh this page without submitting your answers, your progress will be lost.  You are encouraged to open other sections or use notes in different tabs to confirm your answers as the passing score is 100%.

click radiobutton on the left of "click \"splunk\" with \"20\" percent overlap below \"See case studies\""
select "click \"splunk\" with \"20\" percent overlap below \"See case studies\"" from the answers
click the last radiobutton
click 2nd radiobutton "click \"splunk\" with \"20\" percent overlap below \"See case studies\""
A parent suite can also be a child of another suite.
There is no way to know which test cases are inherited from the parent suite.
A parent suite can’t be a child of another suite.
The child suite is selected from inside the parent suite.
For any repetitive set of steps to increase efficiency and improve debugging.
When a test case is running longer than expected.
When the kids misbehave, and they need an easy way to remember the rules.
For one-time scenarios that are unlikely to be repeated.
To handle unexpected scenarios like random pop-ups and ads by automatically adding the rule when certain conditions are met.
To handle scenarios such as login – in case the user gets logged out.
To increase the runtime of each test case.
To send notifications to the test manager for each step in the test.
When the same scenario needs to be tested multiple times using different values
When you need to test a scenario one time with a lot of different variables
When test cases have a lot of different scenarios using global variables
When test cases need a lot of dynamic information
check that page contains "Welcome, ${firstName} ${lastName}!"
check that page contains text and stored values "Welcome, ${firstName} ${lastName}!"
check that page contains the string with parameters "Welcome, ${firstName} ${lastName}!"
check that page contains the string with parameters "Welcome, stored value "firstName" stored value "lastName"!
Pre-defined variables always generate the date or time for the previous day.
Pre-defined variables always generate the current date or time.
Pre-defined variables always generate the date or time for the next day.
Pre-defined variables can’t be configured to a specific time zone.
It selects all the text in paragraph where the link is located.
It does the same thing as a regular click.
It simulates a click with the mouse wheel.
It makes scrolling to the link easier.
When a user wants to click faster.
When the element is part of a browser popup.
When a user wants to target a specific layer of an element.
When the case is running in headless mode.
Multiple correct answers
Because there is no visible UI to drag elements in headless mode.
Because there is a visible UI to drag elements in headless mode.
Because dragging is a mouse-specific action in testRigor, and there is no browser window for a mouse pointer to interact with in headless mode.
Because dragging is a JavaScript-specific action in testRigor, and a browser window is needed to click with JavaScript.
…anywhere on the page below.
…directly below.
…near.
…with “10” percent overlap.

Multiple correct answers
click the element completely below "Additional Data" and on the right of "Nyota"
click the element below "Additional Data" and on the right of "Nyota"
click the element roughly below "Additional Data" and on the right of "Nyota"
click table "Action" at row containing "Nyota" and column "Additional Data"
To use testRigor’s built-in email validations, emails must be sent to an email address with the @testrigor-mail.com domain.
Emails can be sent to any domain to use testRigor’s built-in email validations.
Emails will not be delivered if sent to any other domain besides @testrigor-mail.com.
It is not necessary to specify any domains because all emails are tied directly to the test case they are generated from.
It forces testRigor to focus on the UI instead of a variable.
It is optional when you want to validate against a variable that is visible.
It is necessary to validate against a variable instead of the UI.
It is necessary for all validations.
enter "Yes" into 3rd "Notes"
type "Yes" into the 3rd occurrence of "Notes"
write "Yes" into 3rd "Notes"
type "Yes"
© 2023 testRigor. All rights reserved.