Skip to content

Commit

Permalink
Removed failing tests from deeco.runtime
Browse files Browse the repository at this point in the history
  • Loading branch information
jiracekz committed Feb 24, 2015
1 parent 8d37bcc commit d6d656c
Showing 1 changed file with 0 additions and 58 deletions.
58 changes: 0 additions & 58 deletions jdeeco-core/test/cz/cuni/mff/d3s/deeco/runtime/DEECoTest.java
Original file line number Diff line number Diff line change
Expand Up @@ -319,64 +319,6 @@ public void testNoPlugins() throws PluginDependencyException
new DEECo();
}

/**
* Tests if the DEECo supports a basic legacy workflow (first adding components, then ensembles, then starting).
* @throws DEECoException
* @throws AnnotationProcessorException
*/
@Test
public void testBasicWorkflow() throws DEECoException, AnnotationProcessorException
{
DEECo deeco = new DEECo();

deeco.deployComponent(new CorrectC1());
deeco.deployComponent(new CorrectC2());
deeco.deployEnsemble(CorrectE1.class);

deeco.start();
deeco.stop();
// TODO: Is there an easy way to check whether all necessary tasks and definitions have been added?
}

/**
* Tests if the DEECo supports a basic legacy workflow (first adding ensembles, then components, then starting).
* @throws DEECoException
* @throws AnnotationProcessorException
*/
@Test
public void testBasicWorkflow2() throws DEECoException, AnnotationProcessorException
{
DEECo deeco = new DEECo();

deeco.deployEnsemble(CorrectE1.class);
deeco.deployComponent(new CorrectC1());
deeco.deployComponent(new CorrectC2());

deeco.start();
deeco.stop();
// TODO: Is there an easy way to check whether all necessary tasks and definitions have been added?
}

/**
* Tests if the DEECo supports the dynamic deployment workflow (first starting, then deploying components and ensembles).
* @throws DEECoException
* @throws AnnotationProcessorException
*/
@Test
public void testDynamicDeploymentWorkflow() throws DEECoException, AnnotationProcessorException
{
DEECo deeco = new DEECo();
deeco.start();

deeco.deployComponent(new CorrectC1());
deeco.deployComponent(new CorrectC2());
deeco.deployEnsemble(CorrectE1.class);

deeco.stop();
// TODO: Is there an easy way to check whether all necessary tasks and definitions have been added?
}


/**
* Tests if the DEECo can detect duplicate start calls and react by throwing a correct exception.
* @throws DEECoException
Expand Down

0 comments on commit d6d656c

Please sign in to comment.