network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | Jan 31 '12 at 11:58 | |
| stats | profile views | 0 |
|
Jan 27 |
comment |
Failed automated tests: how to distinguish known and newly introduced bugs? Stephen, thanks for your feedback. Is it possible somehow to have three statuses in Fitnesse? |
|
Jan 26 |
awarded | Student |
|
Jan 26 |
awarded | Editor |
|
Jan 26 |
revised |
Failed automated tests: how to distinguish known and newly introduced bugs? added 75 characters in body |
|
Jan 26 |
comment |
Failed automated tests: how to distinguish known and newly introduced bugs? user246, yes, all your suggestions make sense but I want a clear indication of something happened. No bugs - green. Already known bugs - yellow, new bugs - red. |
|
Jan 26 |
comment |
Failed automated tests: how to distinguish known and newly introduced bugs? Joe, thank you for your thoughts. What would be the best approach to automate comparing of two outputs in Fitnesse? I know how to do comparison in Fitnesse UI but the result is not user-friendly... |
|
Jan 26 |
comment |
Failed automated tests: how to distinguish known and newly introduced bugs? Phil, we have hundreds of test cases under the hood. Automation suite is running every night. So in the morning we want to see if something changed. Say, we see 75 red test cases and we can't easily say whether these are known bugs (we don't have to do anything with them) or new bugs (we should write them into bug tracker). |
|
Jan 26 |
asked | Failed automated tests: how to distinguish known and newly introduced bugs? |
