Package org.camunda.bpm.engine.impl.test
Class PluggableProcessEngineTestCase
java.lang.Object
junit.framework.Assert
junit.framework.TestCase
org.camunda.bpm.engine.impl.test.PvmTestCase
org.camunda.bpm.engine.impl.test.AbstractProcessEngineTestCase
org.camunda.bpm.engine.impl.test.PluggableProcessEngineTestCase
- All Implemented Interfaces:
- junit.framework.Test
Base class for the process engine test cases.
 The main reason not to use our own test support classes is that we need to
 run our test suite with various configurations, e.g. with and without spring,
 standalone or on a server etc.  Those requirements create some complications
 so we think it's best to use a separate base class.  That way it is much easier
 for us to maintain our own codebase and at the same time provide stability
 on the test support classes that we offer as part of our api (in org.camunda.bpm.engine.test).
- Author:
- Tom Baeyens, Joram Barrez
- 
Field SummaryFieldsModifier and TypeFieldDescriptionprotected static ProcessEngineThis class isn't used in the Process Engine test suite anymore.Fields inherited from class org.camunda.bpm.engine.impl.test.AbstractProcessEngineTestCaseauthorizationService, caseService, decisionService, deploymentId, deploymentIds, exception, externalTaskService, filterService, formService, historyService, identityService, managementService, processEngine, processEngineConfiguration, repositoryService, runtimeService, taskService
- 
Constructor SummaryConstructors
- 
Method SummaryMethods inherited from class org.camunda.bpm.engine.impl.test.AbstractProcessEngineTestCaseareJobsAvailable, assertCaseEnded, assertProcessEnded, assertProcessNotEnded, clearServiceReferences, closeDownProcessEngine, deleteDeployments, deleteHistoryCleanupJobs, deployment, deployment, deployment, deployment, deploymentForTenant, deploymentForTenant, deploymentForTenant, deploymentWithBuilder, executeAvailableJobs, executeAvailableJobs, executeAvailableJobs, getInstancesForActivitiyId, getInstancesForActivityId, initializeServices, runAsUser, runBare, waitForJobExecutorOnCondition, waitForJobExecutorOnCondition, waitForJobExecutorToProcessAllJobs, waitForJobExecutorToProcessAllJobsMethods inherited from class org.camunda.bpm.engine.impl.test.PvmTestCaseassertTextPresent, assertTextPresentIgnoreCase, defaultManualActivationMethods inherited from class junit.framework.TestCaseassertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runTest, setName, setUp, tearDown, toString
- 
Field Details- 
cachedProcessEngineThis class isn't used in the Process Engine test suite anymore. However, some Test classes in the following modules still use it: * camunda-engine-plugin-spin * camunda-engine-plugin-connect * camunda-identity-ldap It should be removed once those Test classes are migrated to JUnit 4.
 
- 
- 
Constructor Details- 
PluggableProcessEngineTestCasepublic PluggableProcessEngineTestCase()
 
- 
- 
Method Details- 
initializeProcessEngineprotected void initializeProcessEngine()- Specified by:
- initializeProcessEnginein class- AbstractProcessEngineTestCase
 
- 
getProcessEngine
 
-