How to use data driven approach with TestCafe?

anon17856038 2018-05-03 19:37:25 UTC #1

Hi,
is there any possibility to use data driven approach with Test Cafe?

I want something like this:

[@ annotation to use any data store (json, csv, etc.)]
test ('test', async t => {
// something in here
});

So instead of one test case I want to have 1 x "test data rows amount" test cases.
Maybe you can advice me some additional libraries which I'll be able to combine with Test Cafe?
Do you plan to add this feature in the future?

Thank you.

anon70349247 2018-05-04 07:16:27 UTC #2

You can write a loop around a test to do this.

import data from 'data.json'

for(var i = 0; i>data.length; i++){
    test('test no. ' + i, async t => {
        // something in here
});

anon17856038 2018-05-04 08:31:17 UTC #3

Well, it's not the same, because it will be one test case with one result (fail or not). And it's hard to understand what row of test data failed the test.

I want to see autogenerated test cases depending on test data.
The result should look like:
["test case name" + "test data 1"] - fail / ok
["test case name" + "test data 2"] - fail / ok
etc.

In this case it's easier to find test data for failed test, easier to fix the problem.
But thank you for your proposal.

MarinaRukavitsyna 2018-05-04 08:54:50 UTC #4

Hi @viraxslot
Please take a look at the following solution:

How to pass data between tests?

Is this what you are after?

anon17856038 2018-05-04 09:29:13 UTC #5

@MarinaRukavitsyna
Thank you, I saw this example and I use this approach already. It's not my goal.
Well, maybe examples from another test frameworks could help to understand what I mean.

Links on documentation:
Junit
NUnit
MSUnit

MarinaRukavitsyna 2018-05-04 12:05:59 UTC #6

At present, TestCafe does not provide an API for creating parameterized tests. The only possible workaround is described here.

By the way, the solution provided by Bob should also work for you. Tests will be different, because the cycle is outside a test, not inside.

anon69099579 2018-05-04 13:31:35 UTC #7

@viraxslot I'm not sure how the approach suggested doesn't meet your requirement. For example for this page:

<html>
	<body>
		<div>Hello 0</div>
		<div>Hello 1</div>
		<div>Hello 4</div>
	</body>
</html>

And this test file (I used a global variable to simplify the example):

import { Selector } from "testcafe";

let idx = 0;

fixture("Test") // declare the fixture
    .page(<url>)

for(var i = 0; i < 3 ; i++){
    test('test no. ' + i, async t => {
        await t
            .expect(Selector("div").nth(idx).innerText).eql("Hello " + idx++)
    });
}

I get intelligible output:

 Running tests in:
 - Chrome 66.0.3359 / Windows 8.1.0.0

 Test
 √ test no. 0
 √ test no. 1
 × test no. 2

   1) AssertionError: expected 'Hello 4' to deeply equal 'Hello 2'

      Browser: Chrome 66.0.3359 / Windows 8.1.0.0
.
.
.
 1/3 failed (4s)

anon17856038 2018-05-04 15:12:06 UTC #8

@MarinaRukavitsyna @vastydeep yeah, you're right, it was my mistake. If so, I'll try your proposal in my test cases. Thanks a lot for the understanding.