This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
Part 1: Continuous Delivery Q&A
The remaining questions will be answered this week, so please stay tuned!
Q: What does UAT stand for?
A: User acceptance testing
Q: Who performs UAT in your organization?
A: User acceptance tests or sometimes just known as acceptance tests are ultimately accepted or not accepted by a subject matter expert (could be a stakeholder).
Depending on the requirement this could be for example be the product or business owner. Sometimes, acceptance testing is automated to provide efficiencies; this requires close coordination and collaboration by testing teams (QA) and the business stakeholders.
Q: Do you do any other type of tests before the UAT?
A: Yes there is Unit testing, functional testing, component testing, UI testing. You can refer to the CollabNet webinar “End of Ticketing Hell: Integrating Code Quality“. For more resources: www.collab.net/getci
Q: What do you consider as a successfully finished release?
A: One that has been deployed and is running in production! Or, if we follow the XP (Extreme Programming) convention, “all requirements / user stories have acceptance tests that pass and are accepted by their respective stakeholders for a particular sprint or release.” If you are a Scrum team, your release should meet the criteria for your Definition of Done.
Q: Is the File Release system a front-end to Nexus? Seems like they are equivalent of -SNAPSHOT builds.
A: No, the FRS (TeamForge file release system) is for published, generally available builds, these are typically builds that stakeholders and the community in general, should have access too.
The Nexus artifact repo may also have GA builds however it will also include many development builds (SNAPSHOTS) that result from a continuous build process (CI).
Have a question? Post a comment!