Reporting and Tracking Software Defects
Posted: Wed Apr 04, 2012 2:58 pm
Hi,
We use Ranorex on a very large piece of software, software A, that uses a separate piece of software on the backend, lets call this software B. When a ranorex test fails because of an issue with or change in software B we would write a request/defect for the issue to be fixed and continue running that test. However the issues with software B have begun to stack up and now about 30% of our ranorex tests that get run on our software A fail every time. This is a continuous process and we are consistently adding new tests that sometimes expose issues in software B. We need a way to have these tests failures report as warnings instead of errors/failures so that the test suite shows only the failure rate of software A.
Is this possible to do WITHOUT user code? Changing our tests over to user code every time a defect is found in software B ( about weekly ) is not a possible solution.
Thank you
We use Ranorex on a very large piece of software, software A, that uses a separate piece of software on the backend, lets call this software B. When a ranorex test fails because of an issue with or change in software B we would write a request/defect for the issue to be fixed and continue running that test. However the issues with software B have begun to stack up and now about 30% of our ranorex tests that get run on our software A fail every time. This is a continuous process and we are consistently adding new tests that sometimes expose issues in software B. We need a way to have these tests failures report as warnings instead of errors/failures so that the test suite shows only the failure rate of software A.
Is this possible to do WITHOUT user code? Changing our tests over to user code every time a defect is found in software B ( about weekly ) is not a possible solution.
Thank you