- Java
- Basics
- Classes
- Objects
- Arrays
- Variables
- Loops
- Numbers
- Strings
- Exceptions
- Regexp
- OOP
- Inheritance
- Polymorphism
- Static Keyword
- Abstract Keyword
- Interfaces
- Constructors
- Packages
- Nested Classes
- Final Keyword
- Swing
- Frame
- Panel
- Listener
- Combo Box
- Label
- Image
- Menu
- Table
- Layout
- Drawing
- Timer
- Designer
- Collections
- Lists
- Comparable
- Sets
- Maps
- Generics
- Properties
- Streams
- Json
- Compiler
- Sublime Text
- Apache Ant
- IO
- Streams Io
- Socket
- Watching Files
- Logger
- Clipboard
- Encrypt
- Junit
- About ♣
- Test Case
- Suite Test
- Annotations
- Exceptions
- JavaFX
- Openjfx
- Scene Builder
- First App
- Jar Archive
- On Action
- Change Listener
- Maven
- Demo
- Spring Boot
- Junit
- Guava
- Threads
- Create Thread
- Sleep
- Lock
- Scheduler
JUnit
In unit testing the programmer writes code to verify units of code / JUnit 3 style:T
/**
* JUnit 3 style:
*
* The test class that extends TestCase.
* The methods must start with the word test.
*/
package com.minte9.junit.about_junit;
import junit.framework.TestCase;
public class Junit3Test extends TestCase {
public void testSum() {
int a = 5;
int b = 10;
assertEquals(15, a+b);
}
}
Annotation
The methods that start with @Test annotation are executed as tests / JUnit 4 style:T
/**
* Junit4 style:
*
* Test methods start with @Test annotation.
* You might need to add hamcrest to Referenced Libraries.
*/
package com.minte9.junit.about_junit;
import org.junit.Test;
import static org.junit.Assert.fail;
public class FailTest {
@Test public void mymethod() {
fail("Not implemented yet");
}
}