You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple different moving pieces in the front, editoast and core, in order to make arrival on stop signal a reality. Let's glue all of it together and check that everything works as expected.
Acceptance criteria
it's possible to create a conflict without the arrival on stop signal, but without any conflict once the option is enabled
The text was updated successfully, but these errors were encountered:
Note, it's possible to create an end to end scenario. Note that updating a train is not possible at the moment so you have to create 2 different scenario to demonstrate the functionality.
The original acceptance criteria mentioned an end-to-end test including the UI. At the moment, it's not possible to create such a test since train update under TSv2 is not yet available. That said, testing from UI is not really necessary, what is really important is to exercise editoast API in a scenario with 2 trains and real core simulation and conflict calculations. Such a automated test has been added in #7322 (see 9179115).
Description and goal
There are multiple different moving pieces in the
front
,editoast
andcore
, in order to make arrival on stop signal a reality. Let's glue all of it together and check that everything works as expected.Acceptance criteria
The text was updated successfully, but these errors were encountered: