In this tutorial we show you how to create and execute your first testcase.
To follow this tutorial successfully we recommend you to have a Microsoft SQL Server ready with an installed Adventure Works Sample Database. This sample database can be downloaded from GitHub using the following URL. You can find installation instructions there as well: https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks
You can use another database as well, but in this case you need other SQL queries then we do in this tutorial.
Please ensure that the service account of BiG EVAL has read-permissions on the Adventure Works database.
The following steps must be performed during this tutorial:
We use the ERP database of the sample company Adveture Works in this tutorial. To enable BiG EVAL to access this database you need to create and setup a datasource. This datasource can be used in as many testcases as you want afterwards.
- Click on "Environment" and "Datasources" in the main menu.
- Click on "Create Datasource".
- Enter "AW ERP" as the name and select "OLE DB" as the type of the datasource.
- Change to the tab "Connection" and enter the following connectionstring. Replace SERVER and DATBASE by the respective hostname of your Microsoft SQL Server and the name of the Adventure Works database.
- Ensure that the dialect is set to "Microsoft SQL Server (T-SQL)".
- Click on "Create Datasource" to save the settings.
- Click on "Tests" and "+ Create Test" in the main menu.
- Enter the name "My first test" and click on "Create Test". The Test-Editor gets opend.
- Ensure that the testmethod "Probes exactly equal" is set.
- Switch to the tab "Probes".
- Click on "Add Probe" and "Add dynamic probe". The configuration interface of the new probe gets opened.
- Select the datasourcde we created before.
- Enter the following SQL-Query into the Query-box.
- Ensure that the extraction "Value of the first cell" is selected.
- Click on the button "Validate" to execute the SQL-Query. There should be a success-message when the execution finishes. If there is an error message it usually means that you don't have access to the database. Otherwise you see a respective error message.
- Repeat steps 5 to 9 to add a second probe.
For simplicity reasons we add two identic probes to the testcase during this tutorial. Normally you add two or more different probes.
As soon as you have at least two probes added to the testcase, you are able to execute it. Following we start the testcase manually. There are more possibilities to automate testcase execution, but we do not look at this possibilities within this tutorial.
- Click on the Play-button in the top right corner of the Testcase-Editor to start the test manually. Shortly you see a notification in the messagecenter that tells you that the testcase is currently executing.
- As soon as the testcase finishes, you get another notification that allows you to access detailed testresults using the button "Detailed Results".