Timeline for Testing Unfamiliar Software
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2011 at 13:36 | vote | accept | joshin4colours | ||
| May 17, 2011 at 18:39 | comment | added | corsiKa♦ | Keep in mind that you don't necessarily need either one to be a great tester. You just need to keep a sharp eye for how to break things! Technical ability will give you insight into how to break the program, and domain knowledge will give you insight into how to break the requirements. Both are very useful. But if I had to choose, I'd pick good "tester sense" over either or both any day. | |
| May 17, 2011 at 18:33 | comment | added | joshin4colours | +1 for Technical ability vs Domain knowledge. That is a really helpful distinction, and one I'll keep in mind from now on. | |
| May 17, 2011 at 14:07 | comment | added | user246 | Hah! QA blog says accounting blogs don't sound very interesting. Talk about the pot calling the kettle black. :-) | |
| May 17, 2011 at 3:34 | history | answered | corsiKa♦ | CC BY-SA 3.0 |