How do people handle version labels while performing manual testing when working in a continuous integration environments. In Jira there is a ‘releases’ feature that allows a version to be assigned to an issue's, ‘affects’ and ‘fixed’ fields. But that gets gets out of hand quickly when there are one or more builds a day, and those builds are identified by their git commit ID (hash) not a progressive series.
Before this project I’ve worked with a fast release cycles in manual testing. 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 build.
I’m excited to get started in an agile project again and I want to get it right from the start. What I want to suggest to the team is:
- Builds on check-in identified by hash, and maybe check-in count
- Test on each build
- Builds which break the build AND can’t be immediately fixed are added to Jira as version
- Builds which have major functions implemented or bugs fixed added to Jira as versions
- Bugs are verified and recorded in later check-in numbered builds
- Exploratory testing picks the lasted build recorded in Jira to run through each test session
Does anyone use the Version Merging feature in Jira?