Exam (elaborations)

C857 WGU, Top Questions & Answers, VERIFIED. Rated A+ Testing

3 views 0 purchase

Course
C857 WGU

Institution
C857 WGU

[Show more]

Preview 2 out of 5 pages

View example

Uploaded on June 18, 2023
Number of pages 5
Written in 2022/2023
Type Exam (elaborations)
Contains Questions & answers

c857 wgu
top questions amp answers
verified rate

PassPoint02 Member since 2 year 115 documents sold

CA$11.13

Added

Add to cart Add to wishlist

100% satisfaction guarantee
Immediately available after payment
Both online and in PDF
No strings attached

C857 WGU, Top Questions & Answers,
VERIFIED. Rated A+

Testing

The process of executing a program with the intent of finding

errors.

Black-Box Testing

Also known as datadriven or input/output-driven testing

Be completely unconcerned about the internal behavior and structure of the program. Instead,
concentrate on finding circumstances in which the program does not behave according to its
specifications.

Exhaustive input testing

making use of every possible input condition

as a test case

White-Box Testing

or logic-driven

permits you to examine the internal structure of the program. This strategy derives test data from an
examination of the program’s logic (and often, unfortunately, at the neglect of the specification).

exhaustive path testing

Execute, via test cases, all possible paths of control flow through the program, then possibly the
program has been completely tested.

Vital Program Testing Guidelines

1 A necessary part of a test case is a definition of the expected

output or result.

2 A programmer should avoid attempting to test his or her own

program.

3 A programming organization should not test its own programs.

4 Any testing process should include a thorough inspection of the results of each test.

5 Test cases must be written for input conditions that are invalid

, and unexpected, as well as for those that are valid and expected.

6 Examining a program to see if it does not do what it is supposed to do is only half the battle; the other
half is seeing whether the program does what it is not supposed to do.

7 Avoid throwaway test cases unless the program is truly a

throwaway program.

8 Do not plan a testing effort under the tacit assumption that no errors will be found.

9 The probability of the existence of more errors in a section of a program is proportional to the number
of errors already found in that section.

10 Testing is an extremely creative and intellectually challenging task.

1 A necessary part of a test case is a definition of the expected

output or result.

1. A description of the input data to the program.

2. A precise description of the correct output of the program for that set of input data.

2: A programmer should avoid attempting to test his or her

own program.

They know what the piece is supposed to say, hence may not recognize when it says otherwise. And
they really don’t want to find errors in their own work. The same applies to software authors.

Another problem arises with a change in focus on a software project. After a programmer has
constructively designed and coded a program, it is extremely difficult to suddenly change perspective to
look at the program with a destructive eye.

3: A programming organization should not test its own

programs.

It is more economical for testing to be performed by an objective, independent party.

4: Any testing process should include a thorough inspection of the results of each test.

Errors that are found in later tests were often missed in the results from earlier tests.

5: Test cases must be written for input conditions that are invalid and unexpected, as well as for those
that are valid and expected.

Test cases representing unexpected and invalid input conditions seem to have a higher error detection
yield than do test cases for valid input conditions.

6: Examining a program to see if it does not do what it is supposed to do is only half the battle; the other
half is seeing whether the program does what it is not supposed to do.

Programs must be examined for unwanted side effects.

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying these notes from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller PassPoint02. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for CA$11.13. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

77851 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 14 years now

Start selling

Exam (elaborations)

C857 WGU, Top Questions & Answers, VERIFIED. Rated A+ Testing

Document information

Subjects

Written for

Seller

Reviews received

Content preview