[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-241623-105":3,"detail-sidebar-cat-1-en-105":80,"doc-detail-241623-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","quality-assurance-test-standards-practices-test-strategy-9aad134969","Quality Assurance & Test Standards & Practices - Test Strategy 9AAD134969","","Test Strategy document outlining the verification and validation approach for software applications developed or maintained by ABB software development units or delivered by external vendors. It defines testing phases, relationships between them, and clear entry and exit criteria. The strategy covers risk mitigation for software product quality, the test types performed across phases, and the responsibility distribution. It also specifies intended audiences and usage scenarios for guiding project planning and driving changes to testing execution.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/quality-assurance-test-standards-practices-test-strategy-9aad134969/241623/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/quality-assurance-test-standards-practices-test-strategy-9aad134969/241623.png","ImageObject",442,249,{"name":42,"@type":43},"Aran","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-11","2026-09-12",true,{"@type":52,"interactionType":53,"userInteractionCount":30},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What does the test strategy define in the overall verification and validation process?","Question",{"text":62,"@type":63},"It defines the overall approach to verification and validation, including testing phases, their relationships, and the entry and exit criteria for each phase.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"Who is the intended audience for this document?",{"text":67,"@type":63},"Members of ABB software development units, including Project Managers, Release Managers, Application Managers, Service Managers, Developers, and Testers.",{"name":69,"@type":60,"acceptedAnswer":70},"How does the strategy address software product quality risks?",{"text":71,"@type":63},"It describes how product quality risks are mitigated, which test cases are performed in different test phases, and how testing responsibilities are distributed.","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},241623,1791322801,{"code":4,"msg":81,"data":82},"success",[83,87,92,97,102,107,112,117,122],{"id":84,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":85,"slug":86},11,90,"presentations",{"id":88,"doc_module":22,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},12,"Resumes",80,"resumes",{"id":93,"doc_module":22,"doc_module_name":25,"category_name":94,"show_sort_weight":95,"slug":96},14,"Invoices",70,"invoices",{"id":98,"doc_module":22,"doc_module_name":25,"category_name":99,"show_sort_weight":100,"slug":101},15,"Posters",60,"posters",{"id":103,"doc_module":22,"doc_module_name":25,"category_name":104,"show_sort_weight":105,"slug":106},16,"Social Media",50,"social-media",{"id":108,"doc_module":22,"doc_module_name":25,"category_name":109,"show_sort_weight":110,"slug":111},17,"Forms",40,"forms",{"id":113,"doc_module":22,"doc_module_name":25,"category_name":114,"show_sort_weight":115,"slug":116},18,"Letters",30,"letters",{"id":118,"doc_module":22,"doc_module_name":25,"category_name":119,"show_sort_weight":120,"slug":121},21,"Paper Templates",5,"papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":81,"data":127},{"doc_id":78,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":84,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":135,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":136,"language":137,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":12,"update_tm":141,"read_time":84},137455076865,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","—  \nQUALITY ASSURANCE & TETST-STANDARDS & PRACTICES  \nTest Strategy(9AAD134969) 9AAD134969  \n\n| Department | GF-IS ADM Applications Performance & Excellence (APE) |\n| --- | --- |\n| Approver | Giulio Bitella, Global Department Manager |\n| Owner | Anna Pietras, Quality Assurance Lead (QA) |\n\nFor the latest distributable version of this and other Quality Assurance& Test standards please visit this link to ABB Library.  \nWHAT IS THIS?  \nThis document describes the test strategy for development and maintenance of software applications supported by ABB software development units or delivered by External Vendors. The test strategy lays down the overall approach to verification and validation to the extent it can be generalized for projects.  \nThe testing process follows from the strategy approach: it defines phases of testing, relationships between them and their entry and exit criteria.  \nIntended readers of this document are members of any software development units mainly Project Managers, Release Managers, Application Mangers, Service Managers, Developers and Testers. There are two usage scenarios for this document: (1) as a statement of direction, to drive changes in the way testing is done and (2) to guide projects in planning of their testing activities.  \nAn important part of the strategy is to describe how software product quality risks are mitigated, which test cases are performed in the different test phases, and the distribution of responsibility for the testing.  \n—  \nTABLE OF CONTENTSTable of Contents  \nWHAT IS THIS? .............................................................................................................................. 2  \nOVERVIEW ..................................................................................................................................... 1  \nAssumptions ............................................................................................................................ 1  \nRisks.......................................................................................................................................... 1  \nTEST STRATEGY............................................................................................................................ 2  \nContinuous Testing using CI................................................................................................... 2  \nTest Automation ...................................................................................................................... 2  \nRisk-based approach to testing ............................................................................................. 3  \nRegression testing................................................................................................................... 3  \nTEST PHASES ................................................................................................................................ 4  \nRequirement REVIEW ............................................................................................................... 5  \nDesign review ........................................................................................................................... 6  \nStatic analysis .......................................................................................................................... 7  \nCode review.............................................................................................................................. 8  \nUnit testing .............................................................................................................................. 8  \nComponent Integration testing ............................................................................................. 9  \nFunctional and non-functional testing................................................................................ 10  \nUsability testing ....................................................................................","cbCaiahaMYFbtM4m","https://ap.wps.com/l/cbCaiahaMYFbtM4m","pdf",653030,7,31,"English","# What Is This?\n## Overview\n## Assumptions\n## Risks\n# Test Strategy\n## Continuous Testing using CI\n## Test Automation\n## Risk-based approach to testing\n## Regression testing\n# Test Phases\n## Requirement REVIEW\n## Design review\n## Static analysis\n## Code review\n## Unit testing\n## Component Integration testing\n## Functional and non-functional testing\n## Usability testing\n## Security Testing\n## Performance testing\n## System integration testing\n## User Acceptance Testing\n## Production deployment testing\n# Defect Management\n## Defect Severity\n## Defect Priority\n## Defect Statuses and Lifecycle\n# Entrance Criteria\n## Waterfall approach\n## Agile approach(Scrum)\n# Exit Criteria\n## Waterfall approach\n## Agile approach(Scrum)","[{\"question\":\"What does the test strategy define in the overall verification and validation process?\",\"answer\":\"It defines the overall approach to verification and validation, including testing phases, their relationships, and the entry and exit criteria for each phase.\"},{\"question\":\"Who is the intended audience for this document?\",\"answer\":\"Members of ABB software development units, including Project Managers, Release Managers, Application Managers, Service Managers, Developers, and Testers.\"},{\"question\":\"How does the strategy address software product quality risks?\",\"answer\":\"It describes how product quality risks are mitigated, which test cases are performed in different test phases, and how testing responsibilities are distributed.\"}]","Quality Assurance & Test Standards & Practices - Test Strategy 9AAD134969 | PDF",1789178239]