well… i have no idea also if the console is somehow redirected in case of a webbrowser extension (or for this particular one)
must read a bit to see how we can debug such
LE: does KR have his own console logger?
Still lazy to install it, but I may do it one. day.
If doesnt, is yet again an example of poor design, any such errors are silently catched, known also as bug hidding
Neighter I, this is why I used quotes.
Ctrl-Shift-J worked for me in Chrome.
Attempting to open the ‘malformed’ suite I got this in console:
Relevant code for the error:
So, If I understand the code right, it fails when calling await on loadHTMLFile which is apparently an alias for the .js script I found before.
Why exactly, I have no idea, for that somebody more brave than I am have to look into the code, my knowledge on JS is limited
On the imported script we have:
import { unmarshall } from "../helper-service/parser.js";
----
try {
const testSuite = unmarshall(suiteName, testSuiteHTMLString);
resolve(testSuite);
} catch (error) {
reject(error);
}
Which points to:
So the actual exception seems to be raised somewhere in this script.
See at line 45:
const unmarshall = (suiteName, suiteHTLMString) => {
if (!suiteHTLMString) {
throw "Incorrect format";
}
On the parser script, here may be some clues on what the expected format for the suites / cases may be (or not):
import { TestSuite } from '../../models/test-model/test-suite.js';
import { TestCase } from '../../models/test-model/test-case.js';
import { TestCommand } from '../../models/test-model/test-command.js';
Have fun digging further!
Actually, the exception may be thown here:
try {
let testSuite = new TestSuite(suiteName);
const doc = new DOMParser().parseFromString(suiteHTLMString, "text/html");
const testCaseElements = doc.getElementsByTagName("table");
for (const testCaseElement of testCaseElements) {
const testCase = parseTestCase(testCaseElement);
testSuite.testCases.push(testCase);
}
return testSuite;
} catch (e) {
throw "Incorrect format";
}
@Kalle You may have to dig into the functions defined there (parseBlah, marshall etc) to solve the mistery of what is expected in the input html
Are you here?
Will you pass this issue to the development team?
Hi @kazurayam, noted!


