Files
clio/tests/unit
Sergey Kuznetsov d11e7bc60e fix: Data race in new webserver (#1926)
There was a data race inside `CoroutineGroup` because internal timer was
used from multiple threads in the methods `asyncWait()` and
`onCoroutineComplete()`. Changing `registerForeign()` to spawn to the
same `yield_context` fixes the problem because now the timer is accessed
only from the same coroutine which has an internal strand.

During debugging I also added websocket support for `request_gun` tool.
2025-02-27 15:08:46 +00:00
..
2025-01-31 13:33:20 +00:00
2025-02-03 12:00:59 +00:00
2025-02-25 09:29:24 +00:00
2025-02-25 09:29:24 +00:00
2025-01-02 11:39:31 +00:00
2025-01-23 09:34:00 +00:00
2025-02-21 16:10:25 +00:00
2025-02-21 16:10:25 +00:00
2024-06-27 18:21:30 +01:00

Unit testing

The correctness of new implementations can be verified via running unit tests. Below are the information on how to run unit tests.

Running

To run the unit tests, first build Clio as normal, then execute ./clio_tests to run all unit tests.

Adding Unit Tests

To add unit tests, please create a separate file for the component you are trying to cover (unless it already exists) and use any other existing unit test file as an example.