A GUI Functional Test provides a means of testing your GUI's functionality via Selenium on the cloud, which in turn generates a robust report that will allow you to review how your test performed step-by-step, even providing a recorded video of your test as it executed in the engine's web browser!
You create and run your GUI Functional test, and then you review your GUI Functional Test Report.
- Creating a Test from the UI
- Creating a Test from Your IDE
- Creating a Scriptless Test
- What Are Test Suites and Test Cases?
Creating a Test from the UI
One way how you as a tester can create a GUI Functional Test requires uploading your own Taurus YAML configuration file. All Selenium commands must be executed within said YAML file (as opposed to referencing an external Selenium script file). This is the simplest method for executing a BlazeGrid test.
You can either write your own YAML configuration file from scratch, or you can use the Blazemeter Chrome Extension to automatically generate the file for you.
For more details, check out our guide on Creating a GUI Test from the UI.
Creating a Test from Your IDE
If you as a developer prefer to execute a Selenium Java or Python script, you can do so by modifying your script to communicate with BlazeMeter, then execute the script from your local integrated development environment (IDE), which will in turn automatically create a BlazeGrid test on the cloud.
We have two guides to choose from:
Creating a Scriptless Test
Another way how you as tester can create a GUI Functional Test, even without writing any code, is to create a "scriptless" test. This means you create and edit tests by dropping pre-defined actions and objects into a test scenario. (It's "scriptless" in that you don't have to write the script; BlazeMeter automatically generates the script behind the scenes!)
For more details, refer to our guide on Creating a GUI Functional Test From Predefined Actions.
What Are Test Suites and Test Cases?
On the Test Creation screen, you can optionally organize your tests into test suites. Here, we will clarify what is meant by "test cases" and "test suites".
A test case is a set of one or more steps. For example, the steps to navigate to a URL, fill out a form, and click a button may be organized into a single test case. In the example test report below, we have a test case named "Homepage" that consists of one step, which is navigating to the URL specified:
A test suite is a collection of test cases. You may have one or more test cases in a test suites. The same test case can be associated with several test suites. In the following example, the test case goes to the homepage again, only this time we have designated it as the second test case inside a test suite. In the screenshot, the test suites are named "BlazeDemo Website 1" and "BlazeDemo Website 2":
Note: Remember how we earlier described "pass" messages as green and "fail" messages as red? This latest report example shows both situations.