Skip to main content
8 events
when toggle format what by license comment
Jun 3, 2020 at 13:39 comment added João Farias It's a rewording of some main RST concepts ;) But risk-based testing precedes RST in many years also. I didn't say to him to start from scratch now and all the time, I said he should first explain the risks and then explain how is the current strategy, then people can advice of how to stir the ship. What he's done was to skip the base reasons and say "here is what I have, what testing can I do?". He missed the "testing for what?" part.
Jun 3, 2020 at 13:17 comment added Rsf @JoãoFarias I think you should credit James Bach for your quotes. Even though James has a point in theory, and even though you should know the risks involved, practically you simply can't afford to dismantle a big system to every possible risk and then work backwords to find ways to test the risks.
Jun 3, 2020 at 10:03 comment added Michael Durrant A question about the devs unit tests - do they mock and stub 100% of the external services such as database? If not "unit" tests are actually integrations tests. This is true at a great many companies today.
Jun 3, 2020 at 10:01 history edited Michael Durrant CC BY-SA 4.0
added 15 characters in body
Jun 3, 2020 at 9:59 answer added Michael Durrant timeline score: 2
Jun 2, 2020 at 22:42 comment added João Farias Testing is an investigation activity to answer questions empirically. The question is backward: Given a certain risk, a testing strategy is developed, which includes which techniques, tools, and environments would be used to fulfill it. In summary, you need to first state your context, risks so people can assess how your strategy, tools, and environments fit on them, determining points for improvement.
Jun 2, 2020 at 20:41 review First posts
Jun 3, 2020 at 2:02
Jun 2, 2020 at 20:33 history asked veryqaguy CC BY-SA 4.0