Skip to content

Flow order priority does not match documented behavior #4456

Closed
@robertmcnees

Description

@robertmcnees

Bug description

When using a JobExecutionDecider the behavior is not accurate according to the documentation of DefaultStateTransitionComparator. Specifically

Hence * > foo* > ??? > fo? > foo

Additionally, the actual behavior when running a Job is not consistent with the test results found in DefaultStateTransitionComparatorTests

In almost all test scenarios the documented behavior is not followed.

Environment

Boot 3.1.4
Java 17

Steps to reproduce

See sample GitHub project to be linked in comments below. The JUnit tests have multiple failing scenarios that should pass.

The tests come in 3 different groups, all of which contain failing tests:

  1. Tests based solely on the example found in the documentation
  2. Tests based on the scenarios in DefaultStateTransitionComparator
  3. Tests created from interpretation of the documentation

Expected behavior

The stated documentation should accurate in regards to the priority Flow. All tests in the sample project should pass.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions