alpha testing _ software testing

7/30/2019 Alpha Testing _ Software Testing

1/6

4/27/13 Alpha Testing | Software Testing

rajeevprabhakaran.wordpress.com/tag/alpha-testing/

Types of Testing Comes Under Testing Levels

November 26, 2008 Rajeev Prabhakaran Nair

1. Unit Testing

Unit Testing is primarily carried out by the developers themselvesDeals functional correctness and the completeness of individual program unitsWhite box testing methods are employed

2. Integration Testing

Integration Testing: Deals with testing when several program units are integratedRegression testing: Change of behavior due to modification or addition is called RegressionUsed to bring changes from worst to leastIncremental Integration Testing: Checks out for bugs which encounter when a module has beeintegrated to the existingSmoke Testing: It is the battery of test which checks the basic functionality of program. If faithen the program is not sent for further testing

3. System Testing

System Testing : Deals with testing the whole program system for its intended purposeRecovery testing: System is forced to fail and is checked out how well the system recovers thfailureSecurity Testing: Checks the capability of system to defend itself from hostile attack on programand dataLoad & Stress Testing: The system is tested for max load and extreme stress points are figured ouPerformance Testing: Used to determine the processing speedInstallation Testing: Installation & uninstallation is checked out in the target platform

Software Testing
http://rajeevprabhakaran.wordpress.com/2008/11/26/types-of-testing-comes-under-testing-levels/http://rajeevprabhakaran.wordpress.com/2008/11/26/types-of-testing-comes-under-testing-levels/http://rajeevprabhakaran.wordpress.com/2008/11/26/types-of-testing-comes-under-testing-levels/http://rajeevprabhakaran.wordpress.com/http://rajeevprabhakaran.wordpress.com/2008/11/26/types-of-testing-comes-under-testing-levels/


2/6



4. Acceptance Testing

UAT: ensures that the project satisfies the customer requirementsAlpha Testing : It is the test done by the client at the developers siteBeta Testing : This is the test done by the end-users at the clients siteLong Term Testing : Checks out for faults occurrence in a long term usage of the product

Compatibility Testing : Determines how well the product is substantial to product transition

Which Type of Testing using in your Organization ? Post your answers as

comment or to our Tangler Post a Comment

Posted in software testing. Tags: Alpha Testing, Beta Testing, Compatibility Testing, IncrementalIntegration Testing, Installation testing, integration testing, Load & Stress Testing, Long Term TestingPerformance testing, Recovery testing, Regression Testing, Security testing, Smoke Testing, systemtesting, UAT, unit testing. Leave a Comment

Different Types of Testing

November 20, 2008 Rajeev Prabhakaran NairPerformance testing

a. Performance testing is designed to test run time performance of software within the context of aintegrated system. It is not until all systems elements are fully integrated and certified as free of defecthe true performance of a system can be ascertainedb. Performance tests are often coupled with stress testing and often require both hardware and softwainfrastructure. That is, it is necessary to measure resource utilization in an exacting fashion. Externinstrumentation can monitor intervals, log events. By instrument the system, the tester can uncovesituations that lead to degradations and possible system failureSecurity testingIf your site requires firewalls, encryption, user authentication, financial transactions, or access databases with sensitive data, you may need to test these and also test your sites overall protectioagainst unauthorized internal or external accessExploratory TestingOften taken to mean a creative, internal software test that is not based on formal test plans or test casetesters may be learning the software as they test itBenefits Realization testsWith the increased focus on the value of Business returns obtained from investments in informatiotechnology, this type of test or analysis is becoming more critical. The benefits realization test is a test oanalysis conducted after an application is moved into production in order to determine whether thapplication is likely to deliver the original projected benefits. The analysis is usually conducted by th
http://rajeevprabhakaran.wordpress.com/2008/11/20/different-types-of-testing/http://rajeevprabhakaran.wordpress.com/2008/11/26/types-of-testing-comes-under-testing-levels/#respondhttp://rajeevprabhakaran.wordpress.com/tag/unit-testing/http://rajeevprabhakaran.wordpress.com/tag/uat/http://rajeevprabhakaran.wordpress.com/tag/system-testing/http://rajeevprabhakaran.wordpress.com/tag/smoke-testing/http://rajeevprabhakaran.wordpress.com/tag/security-testing/http://rajeevprabhakaran.wordpress.com/tag/regression-testing/http://rajeevprabhakaran.wordpress.com/tag/recovery-testing/http://rajeevprabhakaran.wordpress.com/tag/performance-testing/http://rajeevprabhakaran.wordpress.com/tag/long-term-testing/http://rajeevprabhakaran.wordpress.com/tag/load-stress-testing/http://rajeevprabhakaran.wordpress.com/tag/integration-testing/http://rajeevprabhakaran.wordpress.com/tag/installation-testing/http://rajeevprabhakaran.wordpress.com/tag/incremental-integration-testing/http://rajeevprabhakaran.wordpress.com/tag/compatibility-testing/http://rajeevprabhakaran.wordpress.com/tag/beta-testing/http://rajeevprabhakaran.wordpress.com/tag/alpha-testing/http://rajeevprabhakaran.wordpress.com/category/software-testing/http://tangler.com/forum/software-testining/topic/53669


3/6



business user or client group who requested the project and results are reported back to executimanagementMutation TestingMutation testing is a method for determining if a set of test data or test cases is useful, by deliberateintroducing various code changes (bugs) and retesting with the original test data/cases to determine the bugs are detected. Proper implementation requires large computational resourcesSanity testing: Typically an initial testing effort to determine if a new software version is performin

well enough to accept it for a major testing effort. For example, if the new software is crashing systemevery 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not bin a sane enough condition to warrant further testing in its current stateSanity testingTypically an initial testing effort to determine if a new software version is performing well enough accept it for a major testing effort, For example, if the new software is crashing systems every minutes, bogging down systems to a crawl, or destroying databases, the software may not be in sane enough condition to warrant further testing in its current stateBuild Acceptance TestsBuild Acceptance Tests should take less than 2-3 hours to complete (15 minutes is typical). These te

cases simply ensure that the application can be built and installed successfully. Other related test caseensure that Testing received the proper Development Release Document plus other build relateinformation (drop point, etc.). The objective is to determine if further testing is possible. If any Level test case fails, the build is returned to developers un-testedSmoke TestsSmoke Tests should be automated and take less than 2-3 hours (20 minutes is typical). These tests casverify the major functionality a high level. The objective is to determine if further testing is possiblThese test cases should emphasize breadth more than depth. All components should be touched, anevery major feature should be tested briefly by the Smoke Test. If any Level 2 test case fails, the build

returned to developers un-testedBug Regression TestingEvery bug that was Open during the previous build, but marked as Fixed, Needs Re-Testing fothe current build under test, will need to be regressed, or re-tested. Once the smoke test is completed, aresolved bugs need to be regressed. It should take between 5 minutes to 1 hour to regress most bugsDatabase TestingDatabase testing done manually in real time, it check the data flow between front end back endObserving that operations, which are operated on front-end is effected on back-end or not.The approach is as follows:While adding a record there front-end check back-end that addition of record is effected or not. S

same for delete, update, Some other database testing checking for mandatory fields, checking foconstraints and rules applied on the table , some time check the procedure using SQL Query analyzerFunctional Testing (or) Business functional testingAll the functions in the applications should be tested against the requirements document to ensure ththe product conforms with what was specified.(They meet functional requirements)Verifies the crucibusiness functions are working in the application. Business functions are generally defined in threquirements Document. Each business function has certain rules, which cant be broken. Whethethey applied to the user interface behavior or data behind the applications. Both levels need to bverified. Business functions may span several windows (or) several menu options, so simply testing tha


4/6



all windows and menus can be used is not enough to verify the business functions. You must verify th

business functions as discrete units of your testing* Study SRS* Identify Unit Functions* For each unit function* Take each input function* Identify Equivalence class

* Form Test cases* Form Test cases for boundary values* From Test cases for Error Guessing* Form Unit function v/s Test cases, Cross Reference MatrixUser Interface Testing (or) structural testingIt verifies whether all the objects of user interface design specifications are met. It examines the spellinof button test, window title test and label test. Checks for the consistency or duplication of acceleratokey letters and examines the positions and alignments of window objectsVolume TestingTesting the applications with voluminous amount of data and see whether the application produces th

anticipated results (Boundary value analysis)Stress TestingTesting the applications response when there is a scarcity for system resourcesLoad TestingIt verifies the performance of the server under stress of many clients requesting data at the same timeInstallation testingThe tester should install the systems to determine whether installation process is viable or not based othe installation guideConfiguration Testing

The system should be tested to determine it works correctly with appropriate software and hardwaconfigurationsCompatibility TestingThe system should be tested to determine whether it is compatible with other systems (applicationthat it needs to interface withDocumentation TestingIt is performed to verify the accuracy and completeness of user documentation1. This testing is done to verify whether the documented functionality matches the softwarfunctionality2. The documentation is easy to follow, comprehensive and well edited

If the application under test has context sensitive help, it must be verified as part of documentatiotestingRecovery/Error TestingTesting how well a system recovers from crashes, hardware failures, or other catastrophic problemsComparison TestingTesting that compares software weaknesses and strengths to competing productsAcceptance TestingAcceptance testing, which black box is testing, will give the client the opportunity to verify the systemfunctionality and usability prior to the system being moved to production. The acceptance test will b


5/6



the responsibility of the client; however, it will be conducted with full support from the project teamThe Test Team will work with the client to develop the acceptance criteriaAlpha TestingTesting of an application when development is nearing completion, Minor design changes may still bmade as a result of such testing. Alpha Testing is typically performed by end-users or others, not bprogrammers or testersBeta Testing

Testing when development and testing are essentially completed and final bugs, problems need to bfound before the final release. Beta Testing is typically done by end-users or others, not bprogrammers or testersRegression TestingThe objective of regression testing is to ensure software remains intact. A baseline set of data and scripwill be maintained and executed to verify changes introduced during the release have not undoneany previous code. Expected results from the baseline are compared to results of the software beinregression tested. All discrepancies will be highlighted and accounted for, before testing proceeds to thnext levelIncremental Integration Testing

Continuous testing of an application as new functionality is recommended. This may require variouaspects of an applications functionality be independent enough to work separately before all parts the program are completed, or that test drivers are developed as needed. This type of testing may bperformed by programmers or by testersUsability TestingTesting for user-friendliness clearly this is subjective and will depend on the targeted end-user ocustomer. User interviews, surveys, video recording of user sessions, and other techniques can be useProgrammers and testers are usually not appropriate as usability testersIntegration Testing

Upon completion of unit testing, integration testing, which is black box testing, will begin. The purposis to ensure distinct components of the application still work in accordance to customer requirementTest sets will be developed with the express purpose of exercising the interfaces between thcomponents. This activity is to be carried out by the Test Team. Integration test will be termed complewhen actual results and expected results are either in line or differences are explainable/acceptabbased on client inputSystem TestingUpon completion of integration testing, the Test Team will begin system testing. During system testinwhich is a black box test, the complete system is configured in a controlled environment to validate iaccuracy and completeness in performing the functions as designed. The system test will simula

production in that it will occur in the production-like test environment and test all of the functions the system that will be required in production. The Test Team will complete the system test. Prior to thsystem test, the unit and integration test results will be reviewed by SQA to ensure all problems havbeen resolved. It is important for higher level testing efforts to understand unresolved problems frothe lower testing levels. System testing is deemed complete when actual results and expected results aeither in line or differences are explainable/acceptable based on client inputParallel/Audit TestingTesting where the user reconciles the output of the new system to the output of the current system tverify the new


6/6



Posted in software testing. Tags: Acceptance Testing, Alpha Testing, Benefits Realization tests, BetaTesting, Bug Regression Testing, Build Acceptance Tests, Business functional testing, ComparisonTesting, Compatibility Testing, Configuration Testing, Database Testing, Documentation Testing,Exploratory Testing, Functional Testing, Installation testing, Load Testing, Mutation Testing,Performance testing, Recovery/Error Testing, Regression Testing, Sanity testing, Security testing,Smoke Tests, Stress Testing, structural testing, Types of Testing, User Interface Testing, VolumeTesting. 29 Comments

Blog at WordPress.com. Theme: Garland by Stefan Nagtegaal and Steven Wittens.
http://acko.net/http://theme.wordpress.com/themes/garland/http://wordpress.com/?ref=footerhttp://rajeevprabhakaran.wordpress.com/2008/11/20/different-types-of-testing/#commentshttp://rajeevprabhakaran.wordpress.com/tag/volume-testing/http://rajeevprabhakaran.wordpress.com/tag/user-interface-testing/http://rajeevprabhakaran.wordpress.com/tag/types-of-testing/http://rajeevprabhakaran.wordpress.com/tag/structural-testing/http://rajeevprabhakaran.wordpress.com/tag/stress-testing/http://rajeevprabhakaran.wordpress.com/tag/smoke-tests/http://rajeevprabhakaran.wordpress.com/tag/security-testing/http://rajeevprabhakaran.wordpress.com/tag/sanity-testing/http://rajeevprabhakaran.wordpress.com/tag/regression-testing/http://rajeevprabhakaran.wordpress.com/tag/recoveryerror-testing/http://rajeevprabhakaran.wordpress.com/tag/performance-testing/http://rajeevprabhakaran.wordpress.com/tag/mutation-testing/http://rajeevprabhakaran.wordpress.com/tag/load-testing/http://rajeevprabhakaran.wordpress.com/tag/installation-testing/http://rajeevprabhakaran.wordpress.com/tag/functional-testing/http://rajeevprabhakaran.wordpress.com/tag/exploratory-testing/http://rajeevprabhakaran.wordpress.com/tag/documentation-testing/http://rajeevprabhakaran.wordpress.com/tag/database-testing/http://rajeevprabhakaran.wordpress.com/tag/configuration-testing/http://rajeevprabhakaran.wordpress.com/tag/compatibility-testing/http://rajeevprabhakaran.wordpress.com/tag/comparison-testing/http://rajeevprabhakaran.wordpress.com/tag/business-functional-testing/http://rajeevprabhakaran.wordpress.com/tag/build-acceptance-tests/http://rajeevprabhakaran.wordpress.com/tag/bug-regression-testing/http://rajeevprabhakaran.wordpress.com/tag/beta-testing/http://rajeevprabhakaran.wordpress.com/tag/benefits-realization-tests/http://rajeevprabhakaran.wordpress.com/tag/alpha-testing/http://rajeevprabhakaran.wordpress.com/tag/acceptance-testing/http://rajeevprabhakaran.wordpress.com/category/software-testing/

alpha testing _ software testing

Documents