Capture pass/fail results at end of test run?
Hello everyone, I was wondering if anyone has come up with a way to capture/publish just the pass/fail result counts from TestComplete at the end of each test run? I'm already publishing t...
Forum Discussion
Hi Allen,
I solved the problem of sharing large .mht files the following way:
1. Create project suite variables to store counts of various test run events such as test starting, test stopping because of error, warning message logged. You can increment these when a event such as OnLogError occurs or from within scripts. I also write some data from theTestItems object into the project suite variables such as the name of the failing test script.
2. Add OnStopTest event to project.
3. Write script for OnStopTest event that takes the counts stored in the project suite variables and formats them into a nice message containing test run metrics (number of tests in run, number of tests failed, number of warning messages, names of the failing test scripts.
Use SaveResultsAs to write the .mht file to a network drive location and give it a unique filename (I use a mix of current date and time to generate the filename).
Use SendMail to send an email notification to others on your project that includes test run metrics and the UNC path of the .mht file.
As a QA Complete user I think you are on the right track for not using QA Complete just for this one piece of functionility.
I solved the problem of sharing large .mht files the following way:
1. Create project suite variables to store counts of various test run events such as test starting, test stopping because of error, warning message logged. You can increment these when a event such as OnLogError occurs or from within scripts. I also write some data from theTestItems object into the project suite variables such as the name of the failing test script.
2. Add OnStopTest event to project.
3. Write script for OnStopTest event that takes the counts stored in the project suite variables and formats them into a nice message containing test run metrics (number of tests in run, number of tests failed, number of warning messages, names of the failing test scripts.
Use SaveResultsAs to write the .mht file to a network drive location and give it a unique filename (I use a mix of current date and time to generate the filename).
Use SendMail to send an email notification to others on your project that includes test run metrics and the UNC path of the .mht file.
As a QA Complete user I think you are on the right track for not using QA Complete just for this one piece of functionility.