Timeline for Estimating a testing project
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2020 at 16:30 | history | edited | MichaelF | CC BY-SA 4.0 |
added 5 characters in body
|
| Mar 20, 2020 at 5:18 | history | edited | JAINAM | CC BY-SA 4.0 |
added 6 characters in body
|
| Jul 27, 2012 at 4:10 | vote | accept | Rakesh Prabhakaran | ||
| Jul 27, 2012 at 4:09 | vote | accept | Rakesh Prabhakaran | ||
| Jul 27, 2012 at 4:10 | |||||
| Jul 4, 2011 at 12:27 | vote | accept | Rakesh Prabhakaran | ||
| Jul 4, 2011 at 12:28 | |||||
| Jul 4, 2011 at 12:27 | vote | accept | Rakesh Prabhakaran | ||
| Jul 4, 2011 at 12:27 | |||||
| May 6, 2011 at 11:45 | comment | added | MichaelF | Very true, although I haven't been in that world. I've done small companies and start-ups where people are all fired up to get projects going. Usually from presenting the idea to the group then scheduling all in the same meeting. | |
| May 5, 2011 at 22:39 | comment | added | Lyndon Vrooman | I think that this is a great list, however, if this is for an enterprise application, don't forget to also look at learning the business logic behind the functional requirements (often forgotten and helps speed up future testing LoE), and time for UAT if it is a part of the QA testing process. | |
| May 5, 2011 at 19:32 | history | answered | MichaelF | CC BY-SA 3.0 |