Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Verifying the behavior of a software system against the expected behavior of that system.
4
votes
6
answers
984
views
How to prevent the vicious circle of testing via customer
The next update for our software is planned and the previous time it went horribly wrong because of regression, bad testing, etc... … My question is: Once we released the update, how do we prevent the vicious circle of testing via customers while not be able to add more unit tests? …