Timeline for Is context-driven testing suitable for all projects?
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| May 14, 2013 at 15:40 | vote | accept | RichardT. | ||
| May 14, 2013 at 15:40 | comment | added | Robert Harvey | Sounds right to me. | |
| May 14, 2013 at 15:39 | comment | added | RichardT. | Thanks, so I hope I get it right - if I can, I should always look for the best suitable solution for that project and not things that generally are thought to be good. But if the customer gives me their testing strategy, I cannot do much about that. | |
| May 14, 2013 at 15:37 | comment | added | Robert Harvey | Someone makes those decisions. It might not be you. Those decisions are either context-driven, or they're not. They are either adapted to the project and its specific concerns, or they're not. If they are, you can consider it a context-driven process. Otherwise, no. | |
| May 14, 2013 at 15:36 | comment | added | RichardT. | Hm, also when I have the choice, I should not try to test online game the same way as I test the medical system (which would be likely possible but too expensive, for example). But when I am just a tester on such a project and cannot choose anything, I cannot be context-driven tester, right? | |
| May 14, 2013 at 15:33 | comment | added | Robert Harvey | That's right. They are saying that there are no universally best practices, that the best practices are the ones that most fully meet the needs of your particular project. I happen to agree with that. When you make a sweeping statement like "this is the one true way, the one way that everyone should follow under all circumstances," you are automatically wrong. | |
| May 14, 2013 at 15:31 | comment | added | RichardT. | I'm sorry but then how does it help? Everyone knows it will be different but if you read that site, they mention that e.g. context aware is not context driven. That following standards is not context driven and that context driven means looking at the details of the project and then choosing the appropriate techniques etc. | |
| May 14, 2013 at 15:31 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 17 characters in body
|
| May 14, 2013 at 15:29 | comment | added | Robert Harvey | Context-driven Testing says that the medical system will be tested differently than the online game. It will require different processes and different regulatory oversight. It will be more rigorous, and probably less agile. As far as I can tell, Context Driven Testing is not a methodology; it is a philosophy. You're still going to have to bring some techniques like TDD and Acceptance Testing to the table. Try to remember that. | |
| May 14, 2013 at 15:25 | history | edited | Robert Harvey | CC BY-SA 3.0 |
added 7 characters in body
|
| May 14, 2013 at 15:25 | comment | added | RichardT. | Thanks, also the point is that (similiarly to agile) some projects just wont allow you to do that? E.g. I doubt that medical system controlling the remote-surgery machine (not sure about the name) could be tester with context-driven approach. | |
| May 14, 2013 at 15:23 | comment | added | Robert Harvey | What they are saying is that your testing process adapts to your project's concerns. That the testing process is going to be different for the first project than it is for the second. That there is no "one size fits all" process. | |
| May 14, 2013 at 15:21 | comment | added | RichardT. | I did read that even on that site but (being a non native speaker) I did not understand what the authors wanted to say - that CDT cannot be applied on the first? That obviously the context is different and testing is not the same in both cases? But it does not answer (maybe just for me) the question whether I could use that or not. | |
| May 14, 2013 at 15:19 | comment | added | Robert Harvey | The Context Driven Testing site specifically addresses that concern. Look at the first example project in my answer, above. | |
| May 14, 2013 at 15:18 | comment | added | RichardT. | No, context driven testing means you are choosing techniques, methods, deliverables etc. in the context of the project, you do not to try to apply "best practices". And what I ask is - what about projects where you simply cannot do that because of standards, regulations, restrictions.. | |
| May 14, 2013 at 15:17 | history | edited | Robert Harvey | CC BY-SA 3.0 |
deleted 8 characters in body
|
| May 14, 2013 at 15:14 | comment | added | Robert Harvey | If context-driven testing is about handing a project to a testing team and allowing that team to come up with their own methodologies, then it doesn't sound like you're using context-driven testing in such a project. | |
| May 14, 2013 at 15:10 | comment | added | RichardT. | Well, how can you choose techniques, delirevables, methods (ie what context driven mentiones) etc. in project where everything is given and you just have to follow? | |
| May 14, 2013 at 14:58 | history | answered | Robert Harvey | CC BY-SA 3.0 |