Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword or section
Like this
0 of .
Results for:
No results containing your search query
P. 1
Software Testing

Software Testing



|Views: 2,235|Likes:
Published by jeyaseelan
Software Testing
Software Testing

More info:

Published by: jeyaseelan on Aug 11, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less





SQA India
is a partnership firm based in India Offering a wide range of Software qualityassurance and I.T. Enabled Services that match the high global standards in terms of efficiencyand accuracy.Welcome to the Software Quality Assurance (QA) and Testing Information Center. It offersarticles, best practices, methodologies, FAQ, guides, books, directories, and tools that are relatedsoftware QA and testing. Popular materials include job interview FAQ, test plan samples, WinRunner FAQ, and more.What is Software Testing?Software testing is more than just error detection;Testing software is operating the software under controlled conditions, to(1) *verify* that it behaves "as specified";(2) to *detect* *errors*, and(3) to *validate* that what has been specified is what the user actually wanted.1. *Verification* is the checking or testing of items, including software, for conformance andconsistency by evaluating the results against pre-specified requirements. [*V**erification: Are webuilding the system right?*].2. *Error Detection*: Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should.3. *Validation* looks at the system correctness – i.e. is the process of checking that what has beenspecified is what the user actually wanted. [*Validation: Are we building the right system?*]In other words, validation checks to see if we are building what the customer wants/needs, andverification checks to see if we are building that system correctly. Both verification and validationare necessary, but different components of any testing activity.The definition of testing according to the ANSI/IEEE 1059 standard is that testing is the process of analysing a software item to detect the differences between existing and required conditions (thatis defects/errors/bugs) and to evaluate the features of the software item. Remember: The purposeof testing is verification, validation and error detection in order to find problems – and the purposeof finding those problems is to get them fixed.Software TestingTesting involves operation of a system or application under controlled conditions and evaluating theresults. Every Test consists of 3 steps :PlanningInputs to be given, results to be obtained and the process to proceed is toplannedExecutionPreparing test environment, Completing the test, and determining test resultsEvaluationcompare the actual test outcome with what the correct outcome should havebeenAutomated TestingAutomated testing is as simple as removing the "human factor" and letting the computer do thethinking. This can be done with integrated debug tests, to much more intricate processes. The ideaof the these tests is to find bugs that are often very challenging or time intensive for human testersto find. This sort of testing can save many man hours and can be more "efficient" in some cases.But it will cost more to ask a developer to write more lines of code into the game (or an externaltool) then it does to pay a tester and there is always the chance there is a bug in the bug testing
program. Reusability is another problem; you may not be able to transfer a testing program fromone title (or platform) to another. And of course, there is always the "human factor" of testing thatcan never truly be replaced.Other successful alternatives or variation: Nothing is infallible. Realistically, a moderate splitof human and automated testing can rule out a wider range of possible bugs, rather than relyingsolely on one or the other. Giving the testere limited access to any automated tools can often helpspeed up the test cycleSQA India could be a useful resource for Software Quality assurance. We follow SoftwareQuality Assurance (SQA) methods that adhere to the quality assurance at every phase of SDLC(Software Development Life Cycle). A quality control checklist is developed for all phases of SDLC.We aim to provide quality and consistent results through automated process that have been testedover time. Purpose of the SQA Plan is to establish a uniform Web / Software DevelopmentProcess, which is applicable throughout the software development life cycle
Welcome to the Software Quality Assurance (QA) and Testing Information Center. It offersarticles, best practices, methodologies, FAQ, guides, books, directories, and tools that are relatedsoftware QA and testing. Popular materials include job interview FAQ, test plan samples, WinRunner FAQ, and more
Our Software Testing Procedure
 A good test effort is driven by questions such as:
How could this software break?
In what possible situations could this software fail to work predictably?Software testing challenges the assumptions, risks, and uncertainty inherent in the work of other disciplines, and addresses those concerns using concrete demonstration and impartial evaluation.Testing focuses primarily on evaluating or assessing product quality, which is realizedthrough the following core practices:
Find and document defects in software quality.
Advise on the perceived software quality.
Validate and prove the assumptions made in design and requirement specifications throughconcrete demonstration.
Validate that the software product works as designed.
Validate that the requirements are implemented appropriately
Testing Methods
White Box
Also called ‘Structural Testing / Glass Box Testing’ is used for testing the code keeping the system specsin mind. Inner working is considered and thus Developers Test..
Mutation Testing
Number of mutants of the same program created with minor changes and none of their resultshould coincide with that of the result of the original program given same test case.
Basic Path Testing
Testing is done based on Flow graph notation, uses Cyclometric complexity & Graph matrices.
Control Structure Testing
The Flow of control execution path is considered for testing. It does also checks :-Conditional Testing : Branch Testing, Domain Testing.Data Flow Testing.Loop testing :Simple, Nested, Conditional, Unstructured Loops.
Black Box
Also called ‘Functional Testing’ as it concentrates on testing of the functionality rather than the internal

Activity (46)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Owolabixidd577092 added this note
ajax248590 liked this
sbr11 liked this
arth_p472 liked this
sridharanchandran liked this
ajax248590 liked this
BSASciti liked this
Abhimanyu Thakur liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->