thesoftwaredesignlab/kraken

Cross-Platform Multi-User Interaction-based Testing for Android and Web Applications

kraken's Issues

properties.json conf doesn't work

properties file doesn't work

Occasional crash on the reporter module

Current Behavior

I would estimate 1/50 chance of crashing when running a test case. It doesn't matter if the test pass or not, the issue pops up sporadically.

Expected behavior

For the reporter not to crash, and kraken not to report a correct test case as failed.

Context

OS, node, etc.

kraken-node: 1.0.24
node: v16.15.0
os: Linux 5.17.5-arch1-1 x86_64 GNU/Linux

More data

As the stacktrace shows it's unrelated to my steps file or what it calls, is an error propagated from inside kraken.

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at Reporter.generateDeviceReport (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_mo
dules/kraken-node/lib/reports/Reporter.js:159:29)
    at Reporter.generateWebReport (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_modul
.=========================================
es/kraken-node/lib/reports/Reporter.js:155:14)
    at Reporter.generateProcessReport (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_m
odules/kraken-node/lib/reports/Reporter.js:141:18)
    at /home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_modules/kraken-node/lib/reports/R
eporter.js:133:19
    at Array.forEach (<anonymous>)
    at Reporter.generateEachDeviceReport (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/nod
e_modules/kraken-node/lib/reports/Reporter.js:129:37)
    at Reporter.saveReport (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_modules/krak
en-node/lib/reports/Reporter.js:59:14)
    at TestScenario.afterExecute (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_module
s/kraken-node/lib/TestScenario.js:123:23)
    at TestScenario.<anonymous> (/home/muniter/projects/msc/p2/pruebas/e2e_testing_assignment/node_modules
/kraken-node/lib/TestScenario.js:91:30)

It is completely unrelated to the test case, which is working correctly every time.go