Why Does Poeple Import org.junit.Assert Statically?
Submitted by: AdministratorPoeple use the static import statement on org.junit.Assert to save coding time on calling its assetion methods. With a normal import statement, assertion method names must qualified with the class name like this:
import org.junit.Assert;
...
Assert.assertEquals(12, message.length());
With a static import statement, assertion method names can be used directly like this:
import static org.junit.Assert.*;
...
assertEquals(12, message.length());
Submitted by: Administrator
import org.junit.Assert;
...
Assert.assertEquals(12, message.length());
With a static import statement, assertion method names can be used directly like this:
import static org.junit.Assert.*;
...
assertEquals(12, message.length());
Submitted by: Administrator
Read Online JUnit Job Interview Questions And Answers
Top JUnit Questions
| ☺ | What Is JUnit? |
| ☺ | Why Does Poeple Import org.junit.Assert Statically? |
| ☺ | How To Wirte a Simple JUnit Test Class? |
| ☺ | Why Do You Use JUnit to Test Your Code? |
| ☺ | How Do You Launch a Debugger When a Test Fails? |
Top Testing Categories
| ☺ | Manual Testing Interview Questions. |
| ☺ | Rational TestSuite Interview Questions. |
| ☺ | QTP Interview Questions. |
| ☺ | Database Testing Interview Questions. |
| ☺ | Software QA Interview Questions. |
