Web-Books
im Austria-Forum
Austria-Forum
Web-Books
Informatik
The Future of Software Quality Assurance
Seite - 34 -
  • Benutzer
  • Version
    • Vollversion
    • Textversion
  • Sprache
    • Deutsch
    • English - Englisch

Seite - 34 - in The Future of Software Quality Assurance

Bild der Seite - 34 -

Bild der Seite - 34 - in The Future of Software Quality Assurance

Text der Seite - 34 -

34 F. Faber deployingandotherprocesses.WithinDevOpsit isbest if teamsstartusingthesame toolsfortheentireSDLC.Thiscanbeawayofbringingteammemberstogetherand make the SDLC clear and coherent. Different skills present in the team can shape theautomation to where it fits theneedsof the entire team. 4.1 Test Automation In testing,moreandmore testsarebeingautomated.Testengineersworkmorewith testing tools and automation supporting their tests. It creates fast feedback loops whichdrivesdevelopmentdesign and release [9]. In DevOpsyouwant to automate asmuchaspossible.Thetestingquadrantdiagram,ascreatedbyBrianMarick,was adopted by Lisa Crispin and Janet Gregory to create the Agile Testing Quadrants [18]. The quadrants show different kinds of tests where automation can play a role. Technology facing tests supporting the team, like unit tests, are automated. Business facing tests supporting the team, like functional tests, can be automated or done manual. These functional tests in DevOps should be automated, based on the DevOps principle “Automate everything you can” [3]. These functional tests are the tests that should be part of customer-centric testing as mentioned before. Technology facing tests critique to the project, however, require mostly tools and are thereforealreadyautomated. The automationof the first three Agile Testing Quadrants should leave time and space for the last quadrant with business facing tests that critique to the product. Thesetestsshouldbedonemanualandcannotbeautomated.Withmultipleskillsets in a DevOps team, it would benefit the team to perform these tests with the team during the time theysavedwith implementedautomation. The test pyramid can help the implementation of test automation. It makes a distinctionbetweentests thatcanbeexecutedfaston lowlevels(unit tests)andtests that are slower to execute (UI tests) [19]. The lower-level tests are most suitable for automation, which is why they are usually fast to execute. The test pyramid combines tests originallyperformedby developers (unit tests) and those performed by test engineers (service, UI tests). This is a testing strategy that will work with DevOps because it is a cross-functional strategy. Engineers in a DevOps team shouldsharetheirknowledgeandexpertisetofullyimplementthis teststrategy.This strategyalso helps teamsmaking testinga sharedresponsibilitywithin the team. 4.2 ContinuousTesting Automated testing can be part of a deployment pipeline and can be part of Continuous Integration, Delivery, or even Deployment. Deployment pipelines are the“automated implementationofyourapplication’sbuild,deploy, test and release process” [9].Thedeploymentpipelinesareaway toempower teams to takecontrol
zurück zum  Buch The Future of Software Quality Assurance"
The Future of Software Quality Assurance
Titel
The Future of Software Quality Assurance
Autor
Stephan Goericke
Verlag
Springer Nature Switzerland AG
Ort
Cham
Datum
2020
Sprache
englisch
Lizenz
CC BY 4.0
ISBN
978-3-030-29509-7
Abmessungen
15.5 x 24.1 cm
Seiten
276
Kategorie
Informatik
Web-Books
Bibliothek
Datenschutz
Impressum
Austria-Forum
Austria-Forum
Web-Books
The Future of Software Quality Assurance