If it is not possible for some reason for the ECUT client to connect to the ECUT server, the stop button is not enabled. The current stop implementation does not shutdown the ECUT server.
There are other stop issues:
- Stop button is enabled when all test cases run and no error or failure occurred.
- Stop does not cause to stop test execution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The current stop implementation needs more attention. Bidirectional communication between EcutClient and EcutServer is needed in order to stop unit test execution on the client side.
This issue is postponed to M4.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are other stop issues:
- Stop button is enabled when all test cases run and no error or failure occurred.
- Stop does not cause to stop test execution.
The current stop implementation needs more attention. Bidirectional communication between EcutClient and EcutServer is needed in order to stop unit test execution on the client side.
This issue is postponed to M4.