Dasboard does not display data using setup() function

[EmpreLuc]

Brief summary

When execute test with 'export default setup()' the dashboard does not shows data.

k6 version

v0.50.0

xk6-dashboard version

v0.7.3-alpha.1

OS

Windows 11

Docker version and image (if applicable)

No response

Steps to reproduce the problem

Executing with export default function setup()

Executing without export default function setup()

Expected behaviour

That dashboard shows data with export default function setup()

Actual behaviour

When execute test with 'export default setup()' the dashboard does not shows data.

[EmpreLuc]

@szkiba

[szkiba]

Hi @EmpreLuc ,

I tried to reproduce it, but it didn't work for me. Could you send me a zip file that contains everything for reproduction?
By the way, the problem is probably not the presence of the setup function (it is more complicated than that)

[EmpreLuc]

Hi @szkiba ,

The test I tried is the next:

`import { check } from "k6";
import http from "k6/http";

export const options = {
"executor": "ramping-vus",
"startVUs": 0,
"stages": [
{ "duration": "2m", "target": 10 },
{ "duration": "5m", "target": 10 },
{ "duration": "2m", "target": 0 }
]
}

export function setup() {
console.log('Example print'));
}

export default function() {
let res = http.get("https://test.loadimpact.com/");
check(res, {
"is status 200": (r) => r.status === 200
});
};
`

Project.zip

xk6-dashboard builded with next command:
xk6 build v0.51.0 --with github.com/grafana/[email protected]

the command to execute the test:
./k6 run -o 'web-dashboard=open=true&report=test-result.html' ./tests\restful-api\test.js

before this comment I tried to upgrade k6 to v0.51.0 but have same result, when the stup function is on the test the dashboard doesnt show graphics, but when comment the setup the graphics appears.

[szkiba]

Hi @EmpreLuc , Thanks for the example script. I managed to find the problem and the fix is almost complete. I will merge soon and then make a release.

[EmpreLuc]

Thank you @szkiba!

[szkiba]

@EmpreLuc,Thank you for your help.
Version v0.7.3 contains the fix.