Files
clio/tests/unit
Alex Kremer 42c970a2a3 Forward feature RPC (#1440)
Fixes #1436 

This is a temporary implementation of the `feature` RPC that will always
return `noPermission` iff `vetoed` is set.
If `vetoed` isn't specified, Clio will always forward the request to
`rippled` instead.

In the future, #1131 will implement a Clio-native `feature` RPC. This
requires specific support from `libxrpl` side and that is not going to
be available till at least 2.2.1, hence the temporary forwarding.

It would be great to review the error message and code so that we pick
the right one from the start.

Co-authored-by: Sergey Kuznetsov <skuznetsov@ripple.com>
2024-06-11 10:51:03 +01:00
..
2024-06-11 10:51:03 +01:00
2024-05-29 09:08:27 -04:00
2024-05-15 14:02:36 +01:00
2024-06-11 10:51:03 +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.