Evaluate Changelogic without registration!
  

Acceptance Test

What is an acceptance test?
Acceptance test is the last safety net before releasing a version to production. The exact requirements of an acceptance test are not dictated by Changelogic; crafting an optimal procedure is left up to project team. While some projects might do away with a simple approving click from an authorized superviser, others might need lengthy approval procedures and thorough release testing.

You can consider using various features Changelogic offers to compile your acceptance test:

To start acceptance of a version, go to the details page of the version, select “Start acceptance” as action and save.



The person who starts the acceptance is assigned to be the manager for the version. The version can be reassigned during acceptance if needed. The manager is responsible for coordinating acceptance activities and making a decision of the outcome.


During acceptance, we suggest running acceptance testcases, performing verification for tasks that are implemented in the version but have not been verified yet. Often it is also a good idea to verify tasks that have been planned for the production release cycle ant then closed with a negative resolution.


There are three possible outcomes of an acceptance:

  • the version can be deemed accepted, meaning that the version is suitable for deployment in production
  • a rejected version is one that deployment in production should be avoided of
  • not known is the result when acceptance did not reach a decision, e.g. because a newer accepted version made it obsolete

When created, all versions have resolution “not known”. The resolution “rejected” may be set at all times; the only way to set resolution “accepted” is through the acceptance.


After acceptance decision is made, the acceptance should be finished by selecting “End acceptance with resolution...” and the correct resolution on the details page of the version.