Tuesday 18th April 2006
by adminSoftware Testing:
What is software testing?
There are many published definitions of software testing, but all these definitions
reduce substantially the same thing: software testing, the process of execution is
Software is in a controlled manner in order to answer the question: " Software
behave as specified? .
Software testing is often used in connection with the terms verification and validation.
The test is the examination or testing of products, including software, for conformance and
Consistency with an associated specification. Software testing is only a kind of
Review, which sought.
· Validation: Are we doing the right job?
· Verification: Are we doing the right job?
The term bug is often used to refer to a problem or an error in a computer. There are software —
Error and hardware failure. The term originated in the United States, at the time
Pioneer computers were built from valves, when a number of previously unexplained
Finally, the errors were moths flying over inside the computer back.
Software of some errors of playing with the software, seems to be a methodical
Approach to software testing is a much more thorough means of identifying errors.
Debugging is therefore an activity that supports the tests, but can not replace testing.
However, no amount of testing can be guaranteed to detect all errors.
Other activities that are often associated with software testing, static analysis and
dynamic analysis. Static analysis examines the source code of software, according to the search
Problems and collect metrics without actually running the code. Dynamic Analysis
looks at the behavior of the software while it is running, to provide information such as
4.2 Outline
A test plan is structured as follows:
a) protocol identiÞer;
b) Introduction;
c) Test items;
d) Features to be tested;
e) functions are not tested;
f) Approach;
g) Item pass / fail criteria;
h. The suspension criteria and resumption) requirements;
i) Test deliverables;
j) Consideration Tasks;
k) environmental requirements;
l) functions;
m) StafÞng and training needs;
n) Schedule;
o) risks and hazards;
p) Approvals.
The sections will be arranged in the sp
Test Article
Identify the test items including their version / revision level. Be sure to include characteristics of their transmission
Media, the impact hardware requirements or indicate the need for logical or physical changes occur
Testing can (for example, programs must begin to be transferred from tape to disk).
Supply references to the following test item documentation, if any:
Requirements speciÞcation;
Design speciÞcation;
Users Guide;
Operations guide;
Installation instructions.
Functions will be tested
Identify all software features and combinations of software features to be tested. Identify the test design
speciÞcation associated with individual Functions and any combination of characteristics.
Properties that are not tested
Identify all functions signiÞcant and combinations of features which are not tested and the reasons.
What does it take to build the best testing organization.
Attitude
Conviction
Killing instinct excavate and deliver
Culture
Efforts to find a passion and no money
Efforts for technology sharing and learning
Strength of Ethics
What we do:
Building silicon with xyz architecture.
to the E-linux to put a picture and then building on it.
Wireless Network support, followed by release.
Some fun time:
1. Reporting takes all and send the report without actually running the Tests. The product received from the customer premises backfired. The industry is not spared error, and this one can be worst.
2.
Templates:
Test Plan / Test Case
Priority and severity states and trade-offs between them, mapping to our jargon-blockers and Crasher.
Release Blocker: Last Grade 1, but the 1 Priority / Blocker () from our point of view:
Examples of extreme cases:
Has anyone on a Microsoft product to come "is win" instead of "Windows, but you will not be able to find them. Why register as a tester because you might find it final weight, but also for the manufacturers / Microsoft is 1/BLOCKER priority.
Test-blockers: is a typical case in which you are the crash bug (blockers) but it is taken only as a last priority of the management. Why?
In one of the instances, a provider had a version of OS, which provides that After installing the OS on a new machine, unplug the cable to the hard drive and operating system to crash and would be totally un-recoverable and released would have to re-install the whole operating system again. Nor the supplier is free, Why? Since providers do not expect end users to do so.
Examples of extreme Cases: S 1, but last priority: Crash
Effective implementation and reporting:
The importance of the logs
Importance of logging in regard to non-logging.
Automation: What does it take to implement.
The Road Ahead:
Notepad Java write files wizard-generated code. Importance of testing.
A couple of URL's that you might prove useful:
http://en.wikipedia.org/wiki/Software_testing
target = "_blank" href = "http://en.wikipedia.org/wiki/Scenario_test"> http://en.wikipedia.org/wiki/Scenario_test
href = "http://en.wikipedia.org/wiki/Test_suite"> http://en.wikipedia.org/wiki/Test_suite
target = "_blank" href = "http://en.wikipedia.org/wiki/Software_engineering"> http://en.wikipedia.org/wiki/Software_engineering
href = "http://en.wikipedia.org/wiki/Test_script"> http://en.wikipedia.org/wiki/Test_script
http://en.wikipedia.org/wiki/Regression_testing
stickyminds.com
whatistesting.com
scriptinganswers.com
perlmonks.com
SQA tester.com
indiantestingboard.org
About the Author:
Abhinav Vaid
Indian Testing Board
Article Source: ArticlesBase.com – A Ground Up Kit for Software Testing
