Tag: testing

a.) Using the Mock class, related to corresponding Test class

b.) Using the reflection if using Jdk 1.3 or higher version

c.) Both a.) & b.)

d.) No way to test it

a.) There is no option to test it in Junit

b.) Modifying the testcase to run with SecurityManager that prevents calling System.exit, then catch the SecurityException.

c.) Remove the System.Exit() line then continue the testing with that methods.

d.) Test it everything as-is.

a.) Reflection provides the option to do this.

b.) Copy the method content into the testcase methods.

c.) Place your tests in the same package as the classes under test.

d.) Can't do the testing for protected methods.

The JUnit JAR file.

b.) Location of your JUnit test classes.

c.) Location of classes to be tested.

d.) JAR files of class libraries that are required by classes to be tested

e.) All of the above

a.) Container class, which used to group multiple test cases into a collection and run them together.

b.) defines test fixture, which contains all the test methods.

c.) interface, which contains the declaration of all the methods, needs to be implemented by Testcases.

d.) None of the above

True

False

CR_ACC_ADC

CR_ADC_ACC

ILM_CREATEACCOUNT

ILM_ADC_CREATEACCOUNT

TERM_BIND_DT

H1SD_TERM_BIND

H1SD_TERBIND

None of the Above

General Process

Vanilla Process

Global Process

Operational Process

Software Design Life Cycle

System Development Life Cycle

Software Development Life Cycle

System Design Life Cycle