|
Written by Edvin Eshagh
|
|
There are many types of software testing strategies; thus, organizations must be selective in determining which testing strategy meets their need. Below outlines over 30 different software testing strategies, which by no means is comprehensive. |
|
Read more...
|
|
|
Written by Edvin Eshagh
|
|
In this article, I’ll briefly touch on Microsoft test framework. |
|
Read more...
|
|
Written by Edvin Eshagh
|
|
Both Black-Box and White-Box software testing strategies have their strength and weaknesses. Each requires specific implementation strategy to maximize testing efforts. |
|
Read more...
|
|
|
Written by Edvin Eshagh
|
|
IEEE 829 defines a systematic approach for software testing, which result in effective testing (test plans, test design, test cases, test procedures, better coverage), effective follow-up to track and minimize rework, Reuse documented test cases/procedures by other personal, and proof that testing was conducted to reach a quality level.
|
|
Read more...
|
|
Written by Edvin Eshagh
|
|
Estimate errors in software system by fault seeding, defect pooling, specify your confidence level in an error free system (i.e. 95% sure), how many hours to test, system reliability, system availibility, defect density, defect removal efficiency, testing effectiveness |
|
Read more...
|
|
|
|
|
<< Start < Prev 1 2 3 4 Next > End >>
|
|
Page 1 of 4 |