All geek questions in one place

Error Lifecycle and Release Suggestions

Our team is currently analyzing our procedures for managing official software releases and integrating with the error life cycle .

What error life cycle model are you using? And why?

For example, suppose formal releases are generated for QA once a week. At what point do you mark errors as resolved?

  • When did the developer make their changes?
  • When were the changes reviewed and merged into the release branch?
  • When was the official release released?

And what process or features of your bug tracking software do you use to track this?

Are there any tips / recommendations / recommendations that you can provide?

+3
source share
1 answer

If you are lucky enough to have a unit test that catches an error, or if you can add a new test that specifically checks for an error, it offers a good and objective measure of resolution.

If you perform continuous assembly with regression testing, then as long as the corresponding test passes through your primary branch, the error can be resolved. The advantage of this is that it makes it easy to examine the error resolved on one branch but not resolved on the other, which will lead to an attempt to integrate at the beginning and measure success.

Depending on your culture, you may want the error to be marked as truly resolved if it passes automatic assemblies in all branches.

, , , , - , - - .

+1

Source: https://habr.com/ru/post/1742045/

More articles:


All Articles