How to easily design and automate test cases.pdf

© 2021 Maveryx srl.
All rights reserved.
How to easily design
and
automate a test case

Summary
• Functional black box testing
• Functional test design & implementation (automation)
• The Google Search example
• Conclusion

Functional Testing
• Functional testing verifies that all functionality of the
application under test operate in conformance with their stated
and implicit specification
• Functional testing checks whether the application under test "do what
is supposed to do“
• (“Alternatively”) Functional testing is the process of attempting
to find discrepancies between the application and its
specification

Black-box Testing
• Black-box testing examines the functionality of an application
without peering into its internal structure.
• Completely unconcerned about the internal structure and behavior of
the application being tested.

Functional Black-box Testing
• Functional black-box testing is a
process of attempting to show
that an application matches its
functional specifications, by
ignoring its internal structure.
• Functionality are tested by
providing them inputs and
examining the outputs against the
functional requirements
• The implementation is not known

What is a test automation?
• In software testing, test automation is the use of a software (called
test automation tool) separated from the software being tested, to
control the execution of tests and the comparison of actual
outcomes with predicted outcomes.

What is a test automation?
• Test Automation is a type of testing in which a software tool
executes without human intervention a set of test scripts by:
• performing test actions against the application under test
• comparing the actual results to the expected behavior
• creating test reports

Benefits of test automation
• Test automation is used to repeat more and more times tasks that
are laborious and time-consuming to do manually
• Automated tests can be run quickly and repeatedly and are more
reliable than manual testing approaches
• Numerous open-source and commercial testing tools exist for all
types of testing (functional, UI, performance, security...) and for all
kinds of applications like desktop, web, and mobile

The Demo Application: Google Search
• For the purposes of this tutorial Google Search is used.

Design Test Case
• Use Case
1. Go to google.com (Google Search page)
2. Type "Maveryx" into the search box
3. Click 'Google Search' button to view results
4. Click on the first result (Maveryx website)

Design Test Case
TEST ACTION EXPECTED OUTCOME
Launch browser and navigate to Google
page at https://www.google.com/
Google search page is displayed
Type "Maveryx" into the search box "Maveryx" is typed into the search box
Click 'Google Search' button to start
searching
Search results are displayed
Click on the first result Maveryx homepage is displayed
This test can be executed manually, or it can be automated

Design Test Script
1. Launch Chrome browser
2. Navigate to URL https://www.google.com/en
3. Assert that the Google search page is displayed
4. Type "Maveryx" into the search box
5. Assert that the string "Maveryx" is typed into the
search box
6. Click the 'Google Search' button
7. Check that the search results are displayed
8. Click on the first result (Maveryx homepage)
9. Check that the Maveryx homepage is displayed

Launch browser and Navigate to the website
To open the Google Search in Chrome browser, create an XML “launch” file like:
In the Java test script add the following lines:
//the Chrome->Google Search launch file path
final String chromeGoogleSearch = System.getProperty("user.dir")+"dataGoogle.xml";
//launch Chrome browser and navigate to Google Search
Bootstrap.startApplication(chromeGoogleSearch);
<?xml version="1.0" encoding="UTF-8"?>
<AUT_DATA>
<EXECUTABLE_PATH></EXECUTABLE_PATH>
<APPLICATION_NAME>CHROME</APPLICATION_NAME>
<TOOLKIT>WEB</TOOLKIT>
<AUT_ARGUMENTS>https://www.google.com/en</AUT_ARGUMENTS>
</AUT_DATA>

Working with the HTML elements
• To work with the web elements such as buttons, texts, etc.
1. Locate the HTML elements to test
2. Perform the test action
• To locate the HTML element to test, Maveryx does NOT use neither
"GUI Maps" nor "Locators".
With Maveryx you can locate the HTML element to test specifying
• identifier (e.g. name, id, title, caption, …)
• type (e.g. button, text, drop-down list, label, …)

Locate the HTML elements
The search text box can be identified by its title = "Search"
The search button can be identified by its caption "Google Search"
identifier
type
type identifier
//the 'Search' text box
GuiText searchBox = new GuiText("Search");
//'Google Search' button
GuiButton search = new GuiButton("Google Search");

Perform test actions
Once located the HTML element you can perform the relevant test action.
In this test:
• enter text into the search box
• click the ‘Google Search’ button
• click an hyperlink (the first search result)
//the Search text box
searchBox.setText(searchKey);//type the search term
//the 'Google Search' button
GuiButton search = new GuiButton("Google Search");
search.click(); //click the 'Google Search' button
//the first item of the search result page
GuiHyperlink result = new GuiHyperlink("Maveryx-Test Automation Tool for GUI Testing");
result.click(); //click it

Check the Results: Assertions
• To compare expected outcomes and the actual outcomes,
assertions can be added to the test script
• expected results = actual results  the test case is PASSED
• expected results ≠ actual results  the test case is FAILED
//check that the string "Maveryx" is inserted into the search box
assertEquals(searchKey, searchBox.getText());
String expectedURL = "https://www.maveryx.com/";
assertEquals(expectedURL, new GuiBrowser().getCurrentPageUrl());//check the
(landing) page url

Check the Results: WaitForObject
• Checking if a test object is present or not in the web page
• The waitForObject function waits until the given object exists.
• Returns if successful (the test object is present)
• Raises an ObjectNotFoundException on failure, if the function times out and the
test object is not present
//the Search text box
//check that the search textbox is present
searchBox.waitForObject(3, 1);
//check whether the landing page is the Maveryx website
new GuiHtmlElement("Trailblazing Functional Automated UI
Testing").waitForObject(3, 1);//the main message is displayed

Conclusion
• Functional black-box testing is the process of attempting to show that
an application matches its specifications, ignoring its implementation
• Start designing the test case than automate it. Remember that to each
test action shall correspond an expected response.
• Automated test scripts in case of web pages or web applications
includes
• identifying web elements
• acting on web elements
• asserting on expected outputs vs. actual outcomes

How to easily design and automate test cases.pdf

More Related Content

What's hot (20)

Similar to How to easily design and automate test cases.pdf (20)

Recently uploaded (20)

How to easily design and automate test cases.pdf