Web-Books
in the Austria-Forum
Austria-Forum
Web-Books
Informatik
The Future of Software Quality Assurance
Page - 96 -
  • User
  • Version
    • full version
    • text only version
  • Language
    • Deutsch - German
    • English

Page - 96 - in The Future of Software Quality Assurance

Image of the Page - 96 -

Image of the Page - 96 - in The Future of Software Quality Assurance

Text of the Page - 96 -

96 M.Mitev 2 Acceptance Testing,Part 2:TheProcess How to organize the process so that you make sure that everythinggoes smoothly? Whatare themost important steps to execute the“perfect”acceptance testing? Toanswer thesequestionswemust startwith thedefinitionofacceptance testing asprovidedbytheISTQB:“formal testingwithrespect touserneeds, requirements, andbusinessprocessesconductedtodeterminewhetherornota systemsatisfies the acceptance criteria and to enable the user, customers or other authorized entity to determinewhetherornot toaccept thesystem.Acceptance testing is also knownas User Acceptance Testing (UAT), end user testing, Operational Acceptance Testing (OAT)orfield (acceptance) testing”. 2.1 Types ofAcceptance Testing There are different types of acceptance testing that should be performed under different circumstances and regulations. For example, the most well known is the useracceptancetestingwherethecriteriafor“done”areusuallycreatedbybusiness customers and expressed in a business domain language. Very popular is also the operation acceptance testing where the criteria are defined in terms of functional and non-functional requirements. Also, contract and regulation acceptance testing are executed where the criteria are defined by agreements or state laws and regulations.Themostwellknownarethealphaandbetaacceptancetesting.Whatdo theyconsistof?Developersofmarket softwareproductsoftenwant toget feedback from potential or existing customers in their market before the software is put for sale commercially.That iswhen it comes toalphaandbeta testing. 2.2 AlphaTesting Alpha testing is performed at the premises of the developing company, not by the developers themselves: usually QAs that were not involved in the project, which providesthecertaintyofanindependentandunaffectedtesting.Thisactivityisquite often outsourced, which even guarantees greater independence of opinion as you will notharmthe reputationand the feelingsofyourcolleagues. 2.3 BetaTesting Beta testing, also known as field testing, is performed by users or potential users at their own location. Many companies, quite often even start-ups consider this
back to the  book The Future of Software Quality Assurance"
The Future of Software Quality Assurance
Title
The Future of Software Quality Assurance
Author
Stephan Goericke
Publisher
Springer Nature Switzerland AG
Location
Cham
Date
2020
Language
English
License
CC BY 4.0
ISBN
978-3-030-29509-7
Size
15.5 x 24.1 cm
Pages
276
Category
Informatik
Web-Books
Library
Privacy
Imprint
Austria-Forum
Austria-Forum
Web-Books
The Future of Software Quality Assurance