(answered) WGU C857 Software Quality Assurance Exam 2023

C857 WGU Software Quality Assurance Exam 2023 successful - Answer A _____ test case is one that detects an undiscovered error. - accomplish goals & minimize unintended actions good - Answer A _____ test case is one that has a high probability of detecting an undiscovered error testing - Answer process of executing a program with the intent of finding errors test case - Answer A _____ _____ must include a description of input data as well as the correct output for that set of input black box - Answer A ________ tester is one that - finds errors - tests usability - focuses on what a program is supposed to do & who it's for white box - Answer A ________ tester focuses exclusively on validating interactions & behaviors that result in functionality - internal behavior & structure reliability - Answer To raise _____ is to find and remove errors. value - Answer To add _____ is to raise quality & reliability gray box - Answer A _____ tester focuses holistically on user actions and the results that return - e.g. integration testing, UI vs code automation - Answer ____ optimizes the testing process & makes testing more efficient - by repeating test cases in a small amount of time code level - Answer tools that assist the developer in identifying and resolving code quality issues test case management system - Answer the best way to document & keep track of test cases - allow for all results to be incorporated - provides a single location for storage ranked list - Answer Building a __________ of defects gives the team the opportunity to voice their concerns so that everyone ends up on the same page. IT-QA - Answer A solid _____ relationship helps deliver compliant business-enabling systems - is fundamental to business success - ensures user requirements are met moderator - Answer inspection session leader - QC engineer - distributes materials & schedule for session - records all errors - ensures errors subsequently corrected inspection - Answer involves team of ~4 people: 1. moderator 2. programmer 3. designer (if different) 4. test specialist - formal, 90-120 minute session - programmer narrates code statements - participants raise questions - checklist of common errors, give to programmer - style/choice feedback - IDs error prone sections early walkthrough - Answer less formal code based test in which a team of 3-5 people mentally execute program w/ test cases for 1-2 hours 1. moderator 2. secretary/recorder 3. tester 1-2 experts or fresh faces data reference - Answer Error that occurs when a variable has an unset or uninitialized value computation - Answer error that occurs when calculations among variables include inconsistent data types data declaration - Answer error type that arises when a variable is not assigned w/ correct length or data type interface - Answer error type that occurs when the number of received params are not equal to the number of set args input/output - Answer error type that arises if all the used files are not opened & closed after use - check whether files explicitly declared & attributes are correct desk checking - Answer A testing technique in which the program code is sequentially executed manually by the reviewer - old & not ideal peer rating - Answer technique of evaluating anonymous programs for overall quality, maintainability, etc - administrator + 6-20 others - each picks 1 good & 1 poor - not really a test bc focus is not on errors decision - Answer white box coverage type states creation of enough test cases that each branch direction must be traversed at least once statement (exhaustive) - Answer white box coverage type Involves execution of all the executable statements in the source code at least once multiple condition - Answer white box coverage type Evaluates each decision for all the combinations of conditions & all points of entry at least once condition - Answer white box coverage type Checks that each state in a decision in the program takes all possible outcomes at least once decision condition - Answer white box coverage type Follows that every condition in a decision and every decision in the program takes all possible outcomes at least once Equivalence Partitioning - Answer black box testing type Divides the input domain of a program into a finite number of classes and then identifies the test cases - highest probability of finding most errors cause effect graphing (view input as cause & test for effect) - Answer black box testing type Shows the connection between a given outcome and all issues that manipulate the outcome - for spec that contains combinations of input conditions Boundary Value Analysis - Answer black box testing type Tests extreme ends or boundaries between partitions of the input values error guessing - Answer test case design technique based on intuitive & expert knowledge of test team members writing test cases around probable types of errors to facilitate efficient design logic coverage - Answer tests that exercise all decision point outcomes at least once & ensure that all statements OR entry points are executed at least once nonincremental - Answer modules are tested independently & combined to form program - less machine time - more parallel - more work incremental - Answer every new module is combined with previously tested modules