Open Pearlking311 opened 5 months ago
Hi @Pearlking311 and thank you for the bug report! I also get error but I get a base HTML page generated. Do you add any other cli parameters when you run the test? Wanted to check so I know that I fix all things when I work on it. When I tested it I used: sitespeed.io test.cjs --multi
Hi @soulgalore, Sorry I missed to include it. I used: sitespeed.io --config D:\DemoblazeConfig.json --multi D:\test2.js DemoblazeConfig.json
I got a fix that I can toll out this weekend, but I also think we are missing something, like we should have something like stopAsError that we could use in a catch block so we don't collect metrics for a test that failed. I'll check if I can do something about it.
A fix for this was released last week + checkout stopAsError in https://www.sitespeed.io/documentation/sitespeed.io/scripting/tutorial-06-Error-handling.html
Have you read the documentation?
URL
https://www.demoblaze.com
What are you trying to accomplish
I have used measure.start and measure.stop in each page. When the script fails before url change, html metrics are not generated.
NOTE: I have manually failed step 3 by inputting incorrect Xpath.
What browser did you use?
Chrome
How to reproduce
Log output