THIS REPO IS DEPRECATED. IT WAS MOVED HERE
Qase TMS TestCafe Reporter
npm install testcafe-reporter-qase
In order to use reporter, you should add meta information to your tests. Meta key should be CID
.
You should assign list of case IDs to it, e.g.:
test
.meta('CID', [1])
('Text typing basics', async (t) => {
await t
});
test
.meta({ CID: [2, 3] })
('Click check boxes and then verify their state', async (t) => {
await t
});
After that you can run your tests by providing custom reporter:
npx testcafe chrome examples/use-page-model -r spec,qase
Qase reporter supports passing parameters using two ways:
using .qaserc
file and using ENV variables.
.qaserc
parameters:
enabled
- Enable reporterapiToken
- Token for API access, you can find more information hereprojectCode
- Code of your project (can be extracted from main page of your project:https://app.qase.io/project/DEMOTR
-DEMOTR
is project code here)runId
- Pass Run IDrunName
- Set custom Run name, when new run is created. Supports two parameters:�TE%
%AGENTS%
runDescription
- Set custom Run description, when new run is createdlogging
- Enabled debug logging from reporter or not
Example configuration file:
{
"enabled": true,
"logging": true,
"apiToken": "a786b45e371e1097c4c78a3211e3a1d23018ceb9",
"projectCode": "PROJECTCODE",
"runName": "TestCafe run �TE% %AGENTS%"
}
Supported ENV variables:
QASE_ENABLED
- Same asenabled
QASE_API_TOKEN
- Same asapiToken
QASE_PROJECT
- Same asprojectCode
QASE_RUN_ID
- Pass Run ID from ENV and override reporter optionsQASE_RUN_NAME
- Same asrunName
QASE_RUN_DESCRIPTION
- Same asrunDescription
QASE_LOGGING
- Same aslogging