Package com.ibm.jbatch.tck.tests.jslxml
Class ParallelContextPropagationTests
- java.lang.Object
-
- com.ibm.jbatch.tck.tests.jslxml.ParallelContextPropagationTests
-
public class ParallelContextPropagationTests extends Object
-
-
Constructor Summary
Constructors Constructor Description ParallelContextPropagationTests()
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description void
afterTest()
void
beforeTest()
void
cleanup()
void
setup(String[] args, Properties props)
void
testPartitionContextPropagation()
void
testSplitFlowContextPropagation()
-
-
-
Method Detail
-
testPartitionContextPropagation
@TCKTest(versions="1.1.WORKING",assertions="The values of JobContext and StepContext can be accessed from an artifact running in a partition.",specRefs={@SpecRef(version="1.0",section="10.9.1",notes="API for JobContext"),@SpecRef(version="1.0",section="10.9.2",notes="API for StepContext")},apiRefs={@APIRef(className="jakarta.batch.runtime.context.JobContext",methodNames={"getProperties","getJobName","getExecutionId","getInstanceId"}),@APIRef(className="jakarta.batch.runtime.context.StepContext",methodNames={"getStepExecutionId","getProperties"})},issueRefs="https://java.net/bugzilla/show_bug.cgi?id=5164",strategy="First, certain JobContext and StepContext values (properties, names, ids, etc.) are checked against hard-coded values within the executing batchlet. Then, a PartitionCollector formats some of the values into a String, which is passed to a PartitionAnalyzer. The PartitionAnalyzer sets the job exit status to this formatted String. Finally, we check that the values obtained by parsing the job exit status correspond with the values obtained from the JobExecution and StepExecution.",notes="There is no particular place in the spec that says that partitions share the same values for the getters tested as the top-level JobContext/StepContext.") public void testPartitionContextPropagation() throws Exception
- Throws:
Exception
-
testSplitFlowContextPropagation
@TCKTest(versions="1.1.WORKING",assertions="The values of JobContext and StepContext can be accessed from an artifact running in a split-flow.",specRefs={@SpecRef(version="1.0",section="10.9.1",notes="API for JobContext"),@SpecRef(version="1.0",section="10.9.2",notes="API for StepContext")},apiRefs={@APIRef(className="jakarta.batch.runtime.context.JobContext",methodNames={"getProperties","getJobName","getExecutionId","getInstanceId"}),@APIRef(className="jakarta.batch.runtime.context.StepContext",methodNames="getStepExecutionId")},issueRefs="https://java.net/bugzilla/show_bug.cgi?id=5164",strategy="First, certain JobContext and StepContext values (properties, names, ids, etc.) are checked against hard-coded values within the executing batchlet. Then, each step within the split-flow (they all use the same batchlet) sets its exit status to a formatted String of these values. Finally, we check that the values obtained by parsing the exit statuses of the steps correspond with the values obtained from the JobExecution and StepExecutions.",notes="There is no particular place in the spec that says that split-flows share the same values for the getters tested as the top-level JobContext/StepContext.") public void testSplitFlowContextPropagation() throws Exception
- Throws:
Exception
-
setup
public void setup(String[] args, Properties props) throws Exception
- Throws:
Exception
-
cleanup
public void cleanup()
-
beforeTest
public void beforeTest() throws ClassNotFoundException
- Throws:
ClassNotFoundException
-
afterTest
public void afterTest()
-
-