Chevron Left
Back to Introduction to Software Testing

Learner Reviews & Feedback for Introduction to Software Testing by University of Minnesota

4.4
stars
780 ratings

About the Course

After completing this course, you will have an understanding of the fundamental principles and processes of software testing. You will have actively created test cases and run them using an automated testing tool. You will being writing and recognizing good test cases, including input data and expected outcomes. After completing this course, you will be able to… - Describe the difference between verification and validation. - Explain the goal of testing. - Use appropriate test terminology in communication; specifically: test fixture, logical test case, concrete test case, test script, test oracle, and fault. - Describe the motivations for white and black box testing. - Compare and contrast test-first and test-last development techniques. - Measure test adequacy using statement and branch coverage. - Reason about the causes and acceptability of and poor coverage - Assess the fault-finding effectiveness of a functional test suite using mutation testing. - Critique black-box and white-box testing, describing the benefits and use of each within the greater development effort. - Distinguish among the expected-value (true), heuristic, consistency (as used in A/B regression), and probability test oracles and select the one best-suited to the testing objective. - Craft unit and integration test cases to detect defects within code and automate these tests using JUnit. To achieve this, students will employ test doubles to support their tests, including stubs (for state verification) and mocks (for behavioral verification) (https://martinfowler.com/articles/mocksArentStubs.html). This course is primarily aimed at those learners interested in any of the following roles: Software Engineer, Software Engineer in Test, Test Automation Engineer, DevOps Engineer, Software Developer, Programmer, Computer Enthusiast. We expect that you should have an understanding of the Java programming language (or any similar object-oriented language and the ability to pick up Java syntax quickly) and some knowledge of the Software Development Lifecycle....

Top reviews

DW

Jun 14, 2022

I like this course very much! The coding assignment is easy but always incldues all the essential things we need to learn. I feel so happy that I jsut finished my first unit testing project.

AH

Aug 27, 2020

I love this course, the explanation is great, the assignments are very challenging. I learned many things from software testing. Thanks, Prof. Mike Whalen and Mr. Kevin Wendt

Filter by:

101 - 125 of 197 Reviews for Introduction to Software Testing

By Shubham R

•

Feb 26, 2023

excellent

By Abu S

•

Apr 22, 2022

satisfied

By ADITYA L C N

•

Nov 8, 2021

fastastic

By Chandrabhaga D

•

Jan 23, 2021

Wonderful

By LALANI D H

•

Feb 1, 2025

sdfasd

By Fuad A R

•

Apr 5, 2022

Great

By Rahul V P

•

Oct 8, 2020

Goood

By Duc D T

•

Feb 17, 2025

GOOD

By Hala A

•

Dec 17, 2024

good

By prince r s

•

Aug 4, 2024

good

By R P V R

•

Aug 24, 2023

good

By Ankit R 1

•

Mar 20, 2023

good

By YATIN M N

•

Sep 3, 2022

GOOD

By Vadla R

•

May 24, 2022

Good

By srushti s

•

Jan 2, 2022

Good

By Rachana S

•

Aug 10, 2021

good

By Raju M

•

May 30, 2021

good

By Ahasanul H

•

Apr 23, 2021

good

By Deleted A

•

Jan 13, 2021

Good

By Naman S

•

Nov 5, 2020

good

By saurabh w

•

Oct 11, 2020

Good

By Andy S D

•

Sep 12, 2023

ok

By 2103A 5

•

Aug 28, 2023

na

By KOLANU S C R

•

Apr 5, 2023

gg

By Jeremy K

•

Apr 29, 2021

The course started with a good overview of goals of testing, different terms used in the field, and how to match tests and tools to the goals. It got us involved in writing tests relatively early, which was good, but then dropped it for too long and loaded up at the end. The middle felt more like a soup of picayune questions, even though I appreciate the need to know the vocabulary. I would have liked to see the assignments sprinkled more in the middle of the class too.

Writing a test plan was a valuable exercise. I think it would have been fairer to present the expectations/rubric before we submitted it. I was also stunned to see the same 2 versions of the assignments (The same 37 or 53 tests) handed in repeatedly by my peers. I believe Coursera needs to invest in turnitin.com or a similar product.

I found it a drag to have to downgrade Java on my machine in order to make the assignments work. Also, Eclipse did not behave well, and I found myself needing to switch over to NetBeans. I would have liked to stick with VS Code, but that seems to work better with Maven than with Gradle.

Overall, I find I now have the vocabulary to describe what I have been doing, a bigger picture of the testing endeavor, and some new specific skills like working with Jacoco and Mockito. I am glad I did it, and I think it gave me new insight into how to do my current job well (and I finally found out what UAT stands for) and positions me better in the job market.