execution trend report vs. execution by test schedule
Our customer has frequent problems with execution trend report, he relies on the data provided by execution by test schedule but unfortunatelly the first one is a graphic report that has a higher acceptance by management. I am not sure how to get a recent snapshot. I can only run the ETL jobs (which are scheduled in JTS, CCM and RQM) and the time stamp of the data ware house screen shot seems to be the ending time of 'Quality Management Jobs for Quality Manager', which surprises me, since Quality Manager is an existing project area but not the one used for development.
Still, once I have a new screen shot, not always I have new data in the execution trend.
Can anybody help me understand the dependencies ?
Still, once I have a new screen shot, not always I have new data in the execution trend.
Can anybody help me understand the dependencies ?
2 answers
Execution by status schedule -> Displays a detailed view of your testing effort,including information about weight, point status, and execution attempts. And this is a live report.
But execution trend report -> Displays the actual test execution progress against the planned progress. This report uses weight to determine how much work is complete, how much work is left, and whether progress is being made as expected.
This is a data warehouse based report so make sure that the data collection jobs have been run successfully.Make sure the TCERs are associated with the test plan and test milestone(s) in the report.
The days behind or ahead of schedule information is based on the date of the last data collection job.
But execution trend report -> Displays the actual test execution progress against the planned progress. This report uses weight to determine how much work is complete, how much work is left, and whether progress is being made as expected.
This is a data warehouse based report so make sure that the data collection jobs have been run successfully.Make sure the TCERs are associated with the test plan and test milestone(s) in the report.
The days behind or ahead of schedule information is based on the date of the last data collection job.