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 4

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

6
votes
percentage of the reports to contain sufficient information to reproduce and then fix the issues. If you want to know how effective your testing is, look at test coverage. If you are doing …
answered Feb 5 '15 by Thomas Owens
5
votes
defects before testing begins as well as monitoring some metrics that relate to the testability of code, such as cyclomatic complexity, the Halstead complexity measures, and cohesion and coupling (you … to your entire quality assurance practices (which include testing). From here, getting familiar with unit testing tools and mocking tools will make it easier for you to implement your testing. …
answered Aug 29 '11 by Thomas Owens
4
votes
Like Mat says in his comment, IEEE Standard 610-1990 has been withdrawn (effective April 20, 2001), which means that it is no longer maintained and the information may be obsolete or erroneous. Altho …
answered Sep 2 '12 by Thomas Owens
12
votes
You are operating on a faulty premise. The code is not a description of the expected behavior, only the requirements and test cases are. And even then, the requirements and tests define two sides of …
answered Oct 18 '11 by Thomas Owens
2
votes
A change control board (CCB) would be helpful to shield the developers from the user requests. A CCB is a group (although it could be an individual) that meets on a regular basis to review the latest …
answered Dec 5 '11 by Thomas Owens
4
votes
The information that should be included in a test report includes: a summary of test results the test ID number and the result of that particular test any problems encountered in testing times when … as it's not necessary to summarize a single test. For every test executed, identify the test by its identifier, note any problems or deficiencies in your testing plan (useful for identifying key …
answered Feb 11 '12 by Thomas Owens
5
votes
It depends on your language and framework. Your test coverage tools are doing the right thing. When you examine test coverage, you want to see what lines of code are executed by tests. Using test cov …
answered Aug 23 by Thomas Owens
0
votes
Although it answers a different question, I think my answer to a question about storing the results of static analysis may be useful here as well. You need to version control your test cases and test …
answered Mar 16 '16 by Thomas Owens
7
votes
addition, these tests can be run as part of smoke testing or regression testing to ensure that later changes have not re-introduced an old defect into the system. The first thing to consider is the level … be more appropriate. If the feature is minor, perhaps the test is no longer necessary at all. You can also consider not only relying on testing, but logging as well. For example, capturing information …
answered May 10 '12 by Thomas Owens
2
votes
DevOps is not the "application of the development processes to operations tasks". There are a few different takes on what DevOps is, but I describe it as a mindset or culture where the deployment, ope …
answered Jun 4 '18 by Thomas Owens
3
votes
If you're looking for formal terminology, I'd forget the term "bug" all together. Only consider mistake, error, fault, and failure. Based on IEEE610.12-90, the definitions are (as provided in the Soft …
answered Aug 31 '12 by Thomas Owens
2
votes
It looks like a couple of graphs. Graphing the number of bugs over time is called defect arrival. If this is a count of total bugs (open, closed, deferred, etc.), this graph is showing a more stable …
answered May 15 '17 by Thomas Owens
0
votes
By the time the code gets to a code review, the developer should have written unit tests, successfully built both the code under review and the unit tests, and have all currently-written unit tests pa …
answered Jul 23 '11 by Thomas Owens
0
votes
. Unit tests are the building blocks of regression and smoke tests, and in some cases can serve as documentation for the intended behavior of a system or pieces of a system. Regression testing is the act … of running most or all of the unit tests on a changed module. This ensures that the changed module continues to work as expected following the changes. Smoke testing is the act of running a (small …
answered Apr 3 '11 by Thomas Owens
3
votes
In a code review, the source code is read by a human. This is often someone other than the original developer, but that's not a requirement. For example, the Personal Software Process enables personal …
answered Jan 11 '12 by Thomas Owens

15 30 50 per page