G'day testers, here goes my first post.
How do people handle versions while performing manual exploratory testing when working in a continuous integration environment. Working in Jira there is a ‘releases’ feature that allows a version to be assigned to an issues, ‘affects’ and ‘fixed’ fields. But that gets gets out of hand quickly when there are one or more builds a day, and those builds a identified by their git hash not a progressive series.
Before this project I’ve worked with a fast release cycle in manual tested. A new build with bug fixes might appear every 3 or 4 days during regression cycles. During regression bugs are verified with any additional checks and then testing just rolls on with the new builds.
I’m excited to get started with a new proper agile project and I want to get it right from the start. What I want to suggest to the team is:
Does anyone use the Version Merging feature in Jira?
>How do people handle versions while performing manual exploratory testing when working in a continuous integration environment.
What is the problem you are trying to solve? Tagging versions in JIRA is a solution, but what is the problem you have in that team?