Timeline for Do I need to test everything?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 11, 2012 at 16:19 | history | suggested | Peter Mortensen | CC BY-SA 3.0 |
Copy edited. (its = possessive, it's = "it is" or "it has".)
|
| Mar 11, 2012 at 16:14 | review | Suggested edits | |||
| S Mar 11, 2012 at 16:19 | |||||
| Mar 10, 2012 at 2:58 | comment | added | Michael Durrant | I wouldn't assume that. If you have ever dealt with obscure browser version behaviors or strange javascript memory issues you've likely gotten quite a workout. More sometimes as back end languages can be a little more reliable and standard. sometimes. Maybe you're talking about static as in html and no javascript though. | |
| Mar 10, 2012 at 2:38 | history | edited | Doug T. | CC BY-SA 3.0 |
deleted 5 characters in body
|
| Mar 10, 2012 at 0:36 | comment | added | Gordon Gustafson | Also, I would assume bugs in a static page would be MUCH easier to fix than logic errors, design errors, and the type of things TDD is normally used to prevent. Both discovering and fixing errors of static pages are likely to be fairly easy, and its my impression that TDD is used to shorten both of those processes when they take longer than is desired. :D | |
| Mar 9, 2012 at 19:26 | vote | accept | Matteo Pagliazzi | ||
| Mar 9, 2012 at 21:53 | |||||
| Mar 9, 2012 at 16:58 | history | answered | Doug T. | CC BY-SA 3.0 |