101 on JUnit and Unit testing

Credits to @bryanminear
Image Link

JUnit is a testing framework/library for Java (programming language). It is used for both unit testing and UI testing. This helps us define the flow of execution of our code.

What is Unit Testing?
"Unit testing is the process of examining a small "unit" of software (usually a single class) to verify that it meets its expectations or specification" (Washington Courses, 2019)

Setting up JUnit
By downloading the newest version of Eclipse, you already have JUnit installed. 
If not here's a guide on how to set it up: Tutorial

Creating a JUnit Test Case in Eclipse
To use properly JUnit you need to create a separate .java file. In this file is were you are actually going to test your class, so name it something significant for example, BoundedQueueTest since in the class im going to test is named BoundedQueue.  
**I'm taking this class from the Introduction to Software Testing book by Paul Ammann and Jeff Offutt.
In the left menu of Eclipse right click on the main class you're testing and select New, then JUnit Test Case.


 A new menu will appear and make sure you select New JUnit 4 Test and select the Next option.
After this another menu of method names will show. In this menu you can choose which methods of your main class you want to test. If you can't find one that suits your test criteria you can always add more manually later.
After this you'll have your Test created.
Eclipse already generates the name of the methods you selected to test like seen on the photo below.


To actually test the method you just need to follow the actually flow of the methods established on the class. Don't worry if the test doesn't pass because if it doesn't you might just found a flaw in the method and you can always improve your code.

Running a JUnit Test
It's very simple just select the Test .java class and click on the little Arrow that's beside the Play green button. Select the Run As option of the menu and finally select the JUnit Test option.


Now you've successfully ran the test. A new side menu called JUnit will apear were you can see the results of your test cases. 
They will appear in green if the test for that method passed and in red if they failed.


In the button you can see a time of console with debug or error messages that can help you figure out why the test failed of passed.

GitHub Repository

References:
https://courses.cs.washington.edu/courses/cse143/11wi/eclipse-tutorial/junit.shtml

Comments

Post a Comment

Popular posts from this blog

Chapters 6.1 & 6.2

Image
Credits to @4vid Image Link 1. What two properties must be satisfied for an input domain to be properly partitioned?  Completeness: The partition must cover all of the domain. Disjoint: blocks should not overlap 2. What is an Input Domain Model (IDM)? Two Approaches to Input Domain Modeling: A. Interface-based approach. 􏰀 Develop characteristics directly from individual input parameters. 􏰀 Just use properties of the domains without considering the actual function under test. B. Functionality-based approach 􏰀 Develop characteristics from a behavioral view of the program under test. 􏰀 Use your understanding of what the system should do. 3. What gives more tests, each choice coverage or pair-wise coverage? Each Choice Coverage (ECC) states that one value from each block for each characteristic must be used in at least one test case. For example, for partitions [A, B] [1, 2] we can get [A, A], [B, B], [1, 1] and [2, 2] which are clearly redundant. Pair-
Read more

Final Exam Questions

1. Software fault: static error in the code. Software error: internal, not a normal behavior of the program due to a fault. Software failure: external, visible failure of the program. That it doesn't work basically. 2. Beizer discussed the goals of testing in terms of the “test process maturity levels” of an organization, where the levels are characterized by the testers’ goals. Level 0: Testing and debugging are the same. (Worst level) Level 1: Testing is only to find that your code doesn't work. Level 2: Get defensive or make an issue personal with testers because they broke your code. Level 3: Understand the job of a tester and take feedback as constructive criticism. Level 4: Become an expert software tester and make extreme good quality software. Work in harmony with testers. 3. Static Code Analysis is usually performed as part of a Code Review (also known as white-box testing). is a method of debugging by examining source code before a program is run . It’s done by ana
Read more

Course evaluation

Image
Credits to @rossf Image Link ECOA Evidence  I've been Ken Bauer's student for almost four years in several different courses, and his teaching method has always been a breath of fresh air. From flip learning to almost conventional teaching (since you grade your own exam) he's not afraid to make changes and give students the chance to explore self learning and to take responsibility on when and how they learn the content of the course. This is a skill that is very important acquire and that is needed on a daily basis in every job in the tech field. Personally i enjoyed the Software Quality and Testing course. There are many students that might not like this method of teaching applied on this course because it requires them to take responsibilities on their own learning and some students can't handle this type of control over their own learning. No negative feedback for this course, only that maybe some classes should be online.
Read more