Welcome to the Concordia 2 documentation! This page will help you to get started fast. If you run into problems, you can find help on our Slack channel.
Concordia Compiler requires only NodeJS 10.14 (or above) and works on Linux, MacOS and Windows.
In this Quick Start, we'll create a simple specification of an interaction with a search page and use Google Chrome. Therefore, download it before continuing.
Step 0: Initialize
If you are starting a new project or whether your project does not have a file named package.json, then run:
It will install version 2 that is in alpha stage, although stable.
Note that the needed package name is concordialang (with lang). After installing it, we'll always use npx concordia to execute it.
Step 2: Configure
1
npx concordia --init
Copied!
Concordia Compiler will ask you about some preferences. Press Enter to answer every question with their default values. It will create a configuration file named .concordiarc and install the selected plug-in and database drivers.
Step 3: Create a feature
Create the folderfeatures :
1
mkdir features
Copied!
Now create the file search.feature withinfeatures, with the following content:
search.feature
1
Feature: Search
2
3
Scenario: Shows results that correspond to the term
4
5
Variant: Search by pressing Enter
6
Given that I am on "https://google.com"
7
WhenI type "concordialang" in <q>
8
AndI press "Enter"
9
AndI wait for 2 seconds
10
ThenI see "npm"
Copied!
About the file:
Feature and Scenario are high-level, business-focused descriptions about the problem to solve. Their sentences are not used to generate test cases. The above example does not describe them.
A Variant describes the expected interaction with the application's user interface (UI) in order to perform a Scenario. Thus, a Variant uses technological vocabulary.
In Concordia, all the interactions with the UI use first person singular ("I"). That "I" represents the actor that is interacting with the application (in the example above, a visitor).
Step 4: Execute
Finally, run
1
npx concordia
Copied!
✨
That's it.Congratulations!
✨
It will:
set the testing environment up (once);
generate a test case file and transformed it into a test script file;
execute the test script file; and
report the test script results.
Your browser should open automatically during this process and the console will report the execution results.
Your directory should now look like this:
1
┃
2
┣ features/
3
┃ ┣ search.feature
4
┃ ┗ search.testcase 🡐 generated test case
5
┣ node_modules/
6
┣ test/
7
┃ ┗ search.js 🡐 generated test script
8
┣ .concordiarc
9
┣ codecept.json
10
┣ package.json
11
┗ package-lock.json
Copied!
The directory node_modules contains installed dependencies, like tools and frameworks, whose versions are managed with package.json and package-lock.json. The file codecept.json has a basic configuration to run CodeceptJS with Google Chrome and you can change it to fit your needs.
The file features/search.testcase should look like this:
search.testcase
1
# Generated with ❤ by Concordia
2
#
3
# THIS IS A GENERATED FILE - MODIFICATIONS CAN BE LOST !
4
5
import "search.feature"
6
7
@generated
8
@scenario(1)
9
@variant(1)
10
Test Case: Search by pressing Enter - 1
11
Given that I am on "https://google.com"
12
WhenI type "concordialang.org" in <q>
13
AndI press "Enter"
14
AndI wait for 2 seconds
15
ThenI see "npm"
Copied!
The Test Case above was produced from the Variant declared in features/search.feature. Some notes about it:
The import clause (line 5) imports the declared file's content.
The tag @generated (line 7) indicates that the Test Case was produced automatically.
The tag @scenario(1) (line 8) indicates that the Test Case belongs to the first Scenario (1).
The tag @variant(1) (line 9) indicates that the Test Case belongs to the first Variant (1) of the Scenario declared previously.
The Test Case (line 10) is named using the Variant's name plus dash (-) and some (incremental) number. Its content is basically the same as the Variant's, since we did not use any other declarations.
The file test/search.js contains the test script produced from features/search.testcase using the selected plug-in. It also contains line comments with references to their corresponding lines and columns in the .testcase file:
search.js
1
// Generated with ❤ by Concordia
2
// source: search.testcase
3
//
4
// THIS IS A GENERATED FILE - MODIFICATIONS CAN BE LOST !
5
6
Feature("Search");
7
8
Scenario("Shows results that correspond to the term | Search by pressing Enter - 1",(I)=>{
9
I.amOnPage("https://google.com");// (11,2)
10
I.fillField("q","concordialang.org");// (12,2)
11
I.pressKey("Enter");// (13,4)
12
I.wait(2);// (14,4)
13
I.see("npm");// (15,2)
14
});
15
Copied!
Concordia Compiler can also generate test data and test oracles for you. All the test cases and test scripts receive line comments that detail the kind of data test case being explored and reference declarations used to produce oracles and test data.
Notes on installation options
You can opt to install Concordia Compiler locally (per project) or globally.
Local installation (recommended)
does not require administrative privileges (i.e., using sudo on Linux or MacOS) to install;
allows every project to have its own, independent installation;
Whether Windows requires administrative privileges to install, right click Windows (Start) menu, click "Command Prompt (Admin)" or alternatively "Windows PowerShell (Admin)", and then proceed with the installation command.
To upgrade Concordia later, change the installation command from install to upgrade.