When the BIT finishes, I need to be able to determine if it passed or failed. If it fails, I need to know why.
But because of the way the test is formatted, it makes it difficult to find out the failures. I checked the log in normal text format and HTML and neither makes it very easy to determine the cause of failure.
At the moment, I parsing the file and checking for "TEST RUN FAILED." If it's found, I fail the test and if not, I pass it. But I need details.
So, is there a list of possible failures I could just look for? So the failure might say, "Memory test failure" or "error allocating ram", etc. If I had a list of possible errors, I could just look for those and that would work for me.
The only tests I'm running are CPU, ODD, RAM, 2D/3D, and disks.
But because of the way the test is formatted, it makes it difficult to find out the failures. I checked the log in normal text format and HTML and neither makes it very easy to determine the cause of failure.
At the moment, I parsing the file and checking for "TEST RUN FAILED." If it's found, I fail the test and if not, I pass it. But I need details.
So, is there a list of possible failures I could just look for? So the failure might say, "Memory test failure" or "error allocating ram", etc. If I had a list of possible errors, I could just look for those and that would work for me.
The only tests I'm running are CPU, ODD, RAM, 2D/3D, and disks.
Comment