camunda-bpm-assert-scenario | Execute Camunda BPM scenarios and verify | BPM library

by camunda Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets(3)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | camunda-bpm-assert-scenario Summary

camunda-bpm-assert-scenario is a Java library typically used in Automation, BPM, Spring Boot, Spring applications. camunda-bpm-assert-scenario has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

The following process scenario has been executed by means of Camunda BPM Assert Scenario and has been visualised with the Camunda BPM Process Test Coverage library:.

Support

Quality

Security

License

Reuse

Support

Quality

Security

License

Reuse

Support

camunda-bpm-assert-scenario has a low active ecosystem.

It has 44 star(s) with 10 fork(s). There are 11 watchers for this library.

It had no major release in the last 6 months.

There are 8 open issues and 17 have been closed. On average issues are closed in 80 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of camunda-bpm-assert-scenario is current.

This Library - Support

Best in #BPM

Average in #BPM

This Library - Support

Best in #BPM

Average in #BPM

Quality

camunda-bpm-assert-scenario has 0 bugs and 533 code smells.

This Library - Quality

Best in #BPM

Average in #BPM

This Library - Quality

Best in #BPM

Average in #BPM

Security

camunda-bpm-assert-scenario has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

camunda-bpm-assert-scenario code analysis shows 0 unresolved vulnerabilities.

There are 5 security hotspots that need review.

This Library - Security

Best in #BPM

Average in #BPM

This Library - Security

Best in #BPM

Average in #BPM

License

camunda-bpm-assert-scenario is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

This Library - License

Best in #BPM

Average in #BPM

This Library - License

Best in #BPM

Average in #BPM

Reuse

camunda-bpm-assert-scenario releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 9785 lines of code, 774 functions and 186 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

This Library - Reuse

Best in #BPM

Average in #BPM

This Library - Reuse

Best in #BPM

Average in #BPM

Top functions reviewed by kandi - BETA

kandi has reviewed camunda-bpm-assert-scenario and discovered the below as its top functions. This is intended to give you an instant insight into camunda-bpm-assert-scenario implemented functionality, and help decide if they suit your requirements.

Moves the next state of the queue

Log a warning message
Marks the phase as being executed
Runs the scenario
Initialise the scenario
Compares two IDs

Executes the call activity

Start the execution

Called when a test case is finished

Gets the process engine

Checks if this class supports the specified method

Get feature name

Creates a new camel case from the input

Get a method

Executes the action

Get the feature package name

Returns the signature

Notifies the risk assignment

Formats the log message

Get all kandi verified functions for this library.

camunda-bpm-assert-scenario Key Features

Execute Camunda BPM "scenarios" and verify your expectations.

camunda-bpm-assert-scenario Examples and Code Snippets

Java

Lines of Code : 23

License : Permissive (Apache-2.0)

Copy


                                    @Test public void testHappyPath() { // "given" part of the test when(process.waitsAtUserTask("CompleteWork")).thenReturn( (task) -> task.complete() ); // "when" part of the test run(process).startByKey("ReadmeProcess").execute(); // "then" part of the test verify(process).hasFinished("WorkFinished"); }
@Test public void testSlowPath() { when(process.waitsAtUserTask("CompleteWork")).thenReturn( (task) -> task.defer("P2DT12H", () -> task.complete()) ); when(process.waitsAtUserTask("RemindColleague")).thenReturn( (task) -> task.complete() ); run(process).startByKey("ReadmeProcess").execute(); verify(process).hasFinished("WorkFinished"); verify(process, times(2)).hasFinished("ColleagueReminded"); }

,Show me more code!

Java

Lines of Code : 20

License : Permissive (Apache-2.0)

Copy


                                    @Mock private ProcessScenario insuranceApplication; ... @Before public void defineHappyScenario() { when(insuranceApplication.waitsAtUserTask("UserTaskDecideAboutApplication")).thenReturn((task) -> taskService.complete(task.getId(), Variables.putValue("approved", true)) ); }
@Test public void testHappyPath() { Scenario.run(insuranceApplication).startByKey("InsuranceApplication").execute(); ... }
@Test public void testHappyPath() { // WHEN we execute the scenario with the default, "happy" waitstate behaviour ... Scenario.run(insuranceApplication).startByKey("InsuranceApplication").execute(); // THEN we expect the process instance to finish with a "happy" end, the application being accepted ... verify(insuranceApplication).hasFinished("EndEventApplicationAccepted"); }

,Add extensive logging to your tests

Java

Lines of Code : 20

License : Permissive (Apache-2.0)

Copy


                                    ... | Started receiveTask 'Wait for documents' (ReceiveTaskWaitForDocuments @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) * Acting on receiveTask 'Wait for documents' (ReceiveTaskWaitForDocuments @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Deferring action on 'Wait for documents' until 2017-01-25 18:10:21 (ReceiveTaskWaitForDocuments @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4 ... | Fast-forwarding scenario to 2017-01-19 18:09:21 |-- Executing timer-transition (BoundaryEventDaily @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Started boundaryTimer 'daily' (BoundaryEventDaily @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Completed boundaryTimer 'daily' (BoundaryEventDaily @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Started sendTask 'Send reminder' (SendTaskSendReminder @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) * Acting on sendTask 'Send reminder' (SendTaskSendReminder @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Completed sendTask 'Send reminder' (SendTaskSendReminder @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Started noneEndEvent 'Reminder sent' (EndEvent_1 @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Completed noneEndEvent 'Reminder sent' (EndEvent_1 @ DocumentRequest # dad1fecf-dda0-11e6-906e-7ebec62e68c4) | Fast-forwarding scenario to 2017-01-20 18:09:21 |-- Executing timer-transition (BoundaryEvent_2 @ InsuranceApplication # dacca880-dda0-11e6-906e-7ebec62e68c4) | Started boundaryTimer '2 days' (BoundaryEvent_2 @ InsuranceApplication # dacca880-dda0-11e6-906e-7ebec62e68c4) | Completed boundaryTimer '2 days' (BoundaryEvent_2 @ InsuranceApplication # dacca880-dda0-11e6-906e-7ebec62e68c4) | Started userTask 'Speed up manual check' (UserTaskSpeedUpManualCheck @ InsuranceApplication # dacca880-dda0-11e6-906e-7ebec62e68c4) ...

Community Discussions

Trending Discussions on camunda-bpm-assert-scenario

How to translate the Java double colon operator (::) to Scala?

Trending Discussions on camunda-bpm-assert-scenario

How to translate the Java double colon operator (::) to Scala?

QUESTION

How to translate the Java double colon operator (::) to Scala?

Asked 2019-Sep-03 at 08:31

I want to use camunda-bpm-assert-scenario in my ScalaTests.

There I have this code with receiveTask::receive:

when(documentRequest.waitsAtReceiveTask("ReceiveTaskWaitForDocuments")).thenReturn((receiveTask) -> {
  receiveTask.defer("P1DT1M", receiveTask::receive);
});

According to answer in Is it possible to use a Java 8 style method references in Scala? I can translate this quite easily to:

receiveTask.defer("P1D", receiveTask.receive _)

But this gives me:

Error:(84, 45) type mismatch;
 found   : Unit
 required: org.camunda.bpm.scenario.defer.Deferred
       receiveTask.defer("P1D", receiveTask.receive _)

This is the receive function:

void receive();

And here is the expected interface:

public interface Deferred {
  void execute() throws Exception;
}

How can I achieve this in Scala? This is not a duplicate of Is it possible to use a Java 8 style method references in Scala?, there is no solution to "Error:(84, 45) type mismatch; ..."

ANSWER

Answered 2019-Sep-03 at 08:20

After reading this stackoverflow answer, I could solve it to:

receiveTask.defer("P1D", new Deferred{
         def execute(): Unit = receiveTask.receive()
       })

Intellij proposed then to convert it to a Single Abstract Method:

receiveTask.defer("P1D", () => receiveTask.receive())

The problem was that receive had also an overloaded function that takes a parameter.

Source https://stackoverflow.com/questions/57766482

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install camunda-bpm-assert-scenario

1. Add a maven test dependency to your project:. 2. Add a mocked ProcessScenario to your test class.

Support

This library is written by Martin Schimak (plexiti) and evolved out of real life project needs at WDW eLab and in close collaboration with the software development team at WDW eLab's Vienna office. It could not have been brought to light without the open mindedness and open source mindedness I experienced with WDW eLab. You rock! :smile:. You want to contribute? You are very welcome! Please contact me directly via eMail.

Find more information at:

Reuse Trending Solutions