Q. An object that simulates a dependent object:-

View solution

Q. An Object which usually knows how its methods are expected to be called:-

View solution

Q. Libraries that can help create mock objects:-

View solution

Q. Test used to test several units in combination as a whole.

View solution

Q. Spring supports web controller testing by providing Servlet API:-

View solution

Q. Base class to access the managed application context through the inherited getApplicationContext() method.

View solution

Q. The TestContext framework provides two test execution listeners related to context management:-

View solution

Q. Interface which can provide access to the managed application context through the protected field applicationContext:-

View solution

Q. In JUnit 4, you can simply run your test with the test runner SpringJUnit4ClassRunner.

View solution

Q. Method to indicate that the application context is dirty.

View solution

Q. In JUnit4, to explicitly specify a Spring-specific test runner for running your test.

View solution

Q. Annotation for SpringJUnit4ClassRunner:-

View solution

Q. This class implements the ApplicationContextAware interface, so you can get access to the managed application context:-

View solution

Q. AbstractJUnit38SpringContext class also implements the ApplicationContextAware interface.

View solution

Q. Spring JUnit 3 legacy support in releases prior to 2.5, your test class can extend the:-

View solution

Q. AbstractDependencyInjectionSpringContextTests supports dependency injection.

View solution

Q. Test fixtures injected from the managed application context by annotating:-

View solution

Q. TestContext support class AbstractJUnit4SpringContextTests, you can also have test fixtures injected from the managed application context.

View solution

Q. Starting from Spring 2.5, the TestContext framework provides a test execution listener related to transaction management:-

View solution

Q. Annotation for TransactionalTestExecutionListener:-

View solution