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
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
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
Results tagged with Search options user 2305

Verifying the behavior of a software system against the expected behavior of that system.

5
votes
The way I see it is that it's not QA's job to test my code. The tester's job is to make sure my code fulfills all the requirements for that task. When I pass something to QA, I make sure they know t …
answered Sep 18 '10 by Tyanna
10
votes
There are a few good reasons to have a dedicated testing team. First, as mentioned above, developers are very good at testing that their code works, but not a breaking it. Also, as you say, a … developer knows what they wrote, but a testing teams knows what should have been written. At times, these two concepts don't match up. One of the jobs of the testing team is to make sure that the software …
answered Aug 23 '11 by Tyanna
16
votes
suite to see if anything breaks. Instead of having to go through every page yourself, you can have a computer do it for you and give you a list of all the tests that broke. Load testing! You can simulate … late night call that the site has crashed. Functional testing takes time to do manually. Yes, it takes long to write the cases, but if you had to sit down with a binder with 500 pages of tests that you …
answered Feb 5 '13 by Tyanna
6
votes
cases produced. Percentage of total application covered in functional testing. Number of bugs found in staging vs production. In the end, your QA team's job is to find the bugs before they get out in …
answered Feb 8 '13 by Tyanna
24
votes
When my team implemented automated UI testing a lot of great things happened. First, the QA team became much more efficient at testing the application as well as more proficient with the … design meetings. This in turn allowed them to be writing the new test suite cases at the same time as the Devs were coding those new features. Also, the stress testing that the test suite we used was …
answered Jul 12 '11 by Tyanna