Timeline for How do you design your test method/function
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2011 at 6:27 | vote | accept | Tarun | ||
| May 30, 2011 at 20:22 | comment | added | Alan | @Tarun - I'm saying it's "easier" - nothing is easy :} | |
| May 30, 2011 at 17:38 | comment | added | Tarun | Alan, I guess you are trying to say that having exclusive verification points for each elements will be easy with IDE like Visual Studio, are you? | |
| May 30, 2011 at 14:35 | comment | added | Alan | This approach works best in an editor that has something like Intellisense in Visual Studio. | |
| May 30, 2011 at 4:44 | comment | added | Tarun | The problem I see with this approach is lots lots of coding. So I could put all these elements in one file, read them from my test script and validate. Now if any of element is missing from application then I would throw one exception at the end of test with appropriate message which says what failed where. I happened to write a blog post on this approach of late. As always, thanks for sharing your views +1 | |
| May 29, 2011 at 18:10 | history | answered | Alan | CC BY-SA 3.0 |