Timeline for Automate the stable build only
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 14, 2021 at 15:26 | comment | added | João Farias | Note: What @pavelsaman and I mentioned about the wording is a bit off-topic. E.g., you said "Test cases were written as per Acceptance Criteria", which dangerously assumes that the A.C. are complete (explicit x tacit knowledge) and its intention was perfectly transcribed into the code and testing. You said "all bugs that were logged during are closed", whereas you said previously "all bugs resolved", which are very different things. Two references about this are "Exploratory Testing 3.0" by James Bach and "Perfect Software" + "Exploring Requirements" by Jerry Weinberg . | |
| Apr 14, 2021 at 15:25 | comment | added | João Farias | + If the goal is actually to create a security net for further development cycles rather than the current one, you may want to focus having your automated checks running at the end of each cycle. | |
| Apr 14, 2021 at 15:21 | comment | added | João Farias | "I am automating so that" Exactly, you have justify the usage of automation in your test strategy in terms of how to helps certain people (your clients (as a tester who develops these automated checks)) to achieve certain goals. Apparently your primary clients are the testers who focus on experiencing and exploration. If they spend most of their testing session time with setup and reporting, rather than exploration and experiencing, you may want to use the automation tools to revert it, executing them before exploration and experiencing. + | |
| Apr 14, 2021 at 13:28 | comment | added | paul |
I don't see any skeption (what's the right word :) ??) here. Let me take an example: Login functionality - 1.Test cases were written as per Acceptance Criteria, 2.All are passing, 3.all bugs that were logged during are closed, next step - let's automation login functionality, verify credentials. Question is- why automation team is asked to take care of steps 2. and 3.. I am automating so that a.you don't have to test it test it manually b. you don't have to test for multiple user credentials.
|
|
| Apr 14, 2021 at 12:45 | comment | added | João Farias | I follow @pavelsaman's points - such wording may be very dangereous. Additionally, I still think a reflection on the question I left by the end of my answer, inside your context, rather than looking for an authorative, context-ignorant, suggestion. | |
| Apr 14, 2021 at 12:40 | comment | added | pavelsaman | @paul: that sounds like the QA is a gatekeeper, last step in the process. and that sounds like a blaming culture when a bug pops up in production. "all manual tests"... hm, you perhaps mean "all tests we imagined at the time of creating them"? exhaustive testing is not possible, hence "we executed all tests" doesn't ever exist. "all bugs resolved"... I'd be skeptical about this as well, perhaps again "all bugs we found have been resolved". | |
| Apr 14, 2021 at 8:43 | comment | added | paul | Stable build means QA signed off, no more enhancements, all manual tests passed, all bugs resolved. | |
| Apr 14, 2021 at 7:57 | history | edited | pavelsaman | CC BY-SA 4.0 |
deleted 4 characters in body
|
| Apr 13, 2021 at 8:30 | history | answered | João Farias | CC BY-SA 4.0 |