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
test:integration for the xrpl package executes tests against existing public proxies. While this type of integration tests is important we should separate it out into its own targetable execution. The reason for this is all other integration tests are running against a locally running rippled server and are not subject to outages.
Pros:
Ability to target only integration tests that run against a local rippled and are not tied to independent infrastructure.
Will allow rerunning just the faucet tests from github as they are a typical single source of a run
Easily identify the source of the failure was faucet tests
Less executions against faucets that inflate developer activity
1/3 of integration test execution is from the faucets tests so running them in parallel will speed up PR builds. This is due to having to wait for ledgers to close on an external chain.
Cons:
Running locally would require running a separate command or possibly a new one that encompasses all tests.
The text was updated successfully, but these errors were encountered:
test:integration
for thexrpl
package executes tests against existing public proxies. While this type of integration tests is important we should separate it out into its own targetable execution. The reason for this is all other integration tests are running against a locally running rippled server and are not subject to outages.Pros:
Cons:
The text was updated successfully, but these errors were encountered: