With a codebase that contains hundreds of scenarios, the cuke-tree HTML report (generated by the "run" command) can be 4MB+ in size. Outputting the data as a JSON file that is loaded by the static HTML when it is opened might consume a lot less space. This gets important in situations like serving the cuke-tree report from a build sever's GUI.
With a codebase that contains hundreds of scenarios, the cuke-tree HTML report (generated by the "run" command) can be 4MB+ in size. Outputting the data as a JSON file that is loaded by the static HTML when it is opened might consume a lot less space. This gets important in situations like serving the cuke-tree report from a build sever's GUI.