Home/ Questions/Q 3489616
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T11:24:59+00:00

Where i am working we have the following issue: Our current test procedure is

  • 0

Where i am working we have the following issue:
Our current test procedure is that our business analyst test the release based on their specifications/tests. If it passes these tests it is given to the quality dept where they test the new release and the entire system to check if something else was broken.

Just to mention that we outsource our development. Unfortunately the release given to us is rarely tested by the developers and thats “the relationship” we have with them these last 7 years….

As a result if the patch/release fails the tests at the functionality testing level or at the quality level with each patch given we need to test the whole thing again not just the release.
Is there a way we can prevent this from happening?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have two options:

    • Separate the code into independent modules so that a patch/change in one module only means you have to re-test that one module. However, due to dependencies this is effective only to a very limited degree.
    • Introduce automated tests so that re-testing is not as expensive. It takes some more work at fist, but will definitely pay off in your scenario. You don’t have to do unit test or TDD – integration tests based on capture-replay tools are often easier to introduce in your scenario (established project with manual testing process).
    • 0