Software Testing

:
What is software testing?
There are many definitions, published by software testing, but all these definitions
let it boil down to essentially the same thing: software testing is the process of running software in a controlled way to answer the question “Does the software behave as specified?”.
Software testing is often used in combination with the verification and validation of the terms used.
The audit is the examination or testing of products, including software, compliance, and /> Compliance associated with a specification. Software testing is only one type of review, which also uses techniques such as tests, examinations, inspections and walkthroughs. Validation is the process of examining what has been stated is what the user really wanted.
· Validation: Are we doing the job?
• Verification: Are we done a good job?
The error term is often used to describe a problem or an error in a computer. It
Software
Bugs bugs and hardware. The concept emerged in the United States if
Computer engineers were at valves, when a series of />
Defects were eventually discovered that the moths in the belly of the computer.
Software testing should not be confused with debugging. Debugging is the process of
Analysis and localization of errors when the software behave as expected. Although
Identifying some bugs are obviously with the software, play a methodical
Approach to software testing is a much more thorough identification of errors.
Debugging is an activity that supports testing, but can not replace testing.
However, no guarantee level of testing to detect any errors.
Other activities that are often associated with software testing and static analysis are associated
dynamic analysis. Static analysis examines the software’s source code in search of
Problems and measures for the collection, without actually execute the code.
Dynamic Analysis
observed the behavior of the software during execution, to provide information such as
4.2 Overview
A test plan is structured as follows:
a) identiÞer test plan;
b) Introduction;
c) test items;
To test d) functions,
e) functions are not tested;
f) Approach;
g) Item pass / fail;
h) the criteria and requirements for a resumption of the suspension,
i) Test deliverables;
j) Audit functions;
k) environmental requirements;
l) Responsibilities;
m) StafÞng and training needs;
n) Schedule;
o) risks and hazards;
p) Approvals.
Sections should be placed in the />
Test article
Identify the control points, including their version of the revision /. Enter the dimensions of its transmission
Media that show the hardware requirements of impact or the need for logical or physical changes to
can begin tests (such as programs from the tape must be transferred to the hard drive).
Supply references to the test documentation number, if it exists:
speciÞcation needs;
speciÞcation Design;
User Guide;
Operations Guide;
Installation Guide.
Features test
Identify testing all software features and combinations of software functions. Cause />
speciÞcation with each function and combination of characteristics assigned.
Features not to be tested
Identify all features and combinations of features, which tested and will not signiÞcant why.
What it takes to build and test the best organization.

Attitude

Conviction
Killing instinct to dig and deliver

Culture
Work with passion, not money
To support the technology, sharing and learning
Power of Ethics
What we do:
Silicon Architecture Building xyz.
Set the e-Linux to build an image and then set on top.
supports wireless network followed by a release.
Some fun time:
1st Reporting passes all and send the report without actually carrying out the tests. The product against the customer’s premises become. The industry is not spared the mistakes, and it could be worse.
2nd
Models:
Test Plan / Test Case
Priority and statements of gravity and balance between them, the assignment of our jargon and Crasher Blocker.
Blockers Release: Last Grade 1, but the first priority /
blockers (from our point of view):
Examples of extreme cases:
Has anyone encountered a Microsoft product that says “win” instead of “Windows, but you will not find in a position to be. Why, because as a tester that you may be logging as heavy load, but the seller / Microsoft 1 / BLOCKER this priority.
Test-blockers: This is a typical case in which a compound of the crash bug (blocker), but it is considered a last priority by management. Why?
In one case, a manufacturer of a version of the operating system, which states that freed after installation the OS on a new machine, pull the cable to the hard drive crash and the operating system and would be very repayment is not and should reinstall the whole new operating system. But the seller was published, why? Because the seller can not wait to do the user.
Examples of extreme cases: S 1, but this priority:
Crash
Effective and Reporting:
Importance of logs
Importance of forestry to no longer use the connection.
Automation: What happens to implement.
The Road Ahead:
Notepad to write files to Java code-generating wizards. Significance tests.
A pair />

http://en.wikipedia.org/wiki/Software_testing

Http: / / en.wikipedia.org / wiki / Scenario_test

Http: / / en.wikipedia.org / wiki / Test_suite

Http: / / en.wikipedia.org / wiki / software_engineering

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

Software supervision