Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you start a Server Job Unit Test execution and the job status never changes to the Queued/Running state, or the 'Starting Job...' message does not appear in the job log, then it is likely that the preparation phase of Unit Testing failed and the job execution never started.

...

Diagnostics

Errors can be diagnosed by looking at the Unit Testing log which is written to <Project Root Directory>/&PH&/DSU.STUB.log on the DataStage engine where <Project Root Directory> is usually $DSHOME/../Projects/<Project Name>/.

Solution

A common error is that customers forget to add Default Credentials to the engine mapping. Without these the Java Unit Test Harness can't authenticate with Universe. The credentials don't need to be dsadm but that is a common choice.

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@873786c5
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel in ( "serverjob" , "unittesting" , "logging" ) and type = "page" and space = "MCIDOC"
labelsunittesting serverjob logging

Page Properties
hiddentrue

Related issues