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.
6
votes
Is it correct to fix bugs without adding new features when releasing software for system tes...
I would say instead that each release of new features should be on a separate branch. This allows development and releases to be decoupled.
3
votes
Accepted
How to test something on a machine of another type than mine?
Summarizing what is in the comments for the specific problem of needing to confirm compatibility on a Macintosh:
Ensure all parts of the script are POSIX compliant
Borrow a Mac from someone
Install …
505
votes
Leaving intentional bugs in code for testers to find
It should be "you have to keep the test suites up-to-date to account for new features and ensure all high coverage of testing. … If this does not result in finding bugs, then the testing procedures are not sufficiently sophisticated for the product. …