Improve integration testing (file organization, time, memory)

.circleci/config.yml

@@ -60,8 +60,9 @@ jobs:
           name: Verify lockfile
           command: cargo update -w --locked
       - run:
-          name: Build
-          command: cargo build --release
+          # Despite later running cargo build --release, this step is executed on all targets, so might discover testing code issues
+          name: Check
+          command: cargo check --workspace --all-targets
       - run:
           name: Clippy check
           command: ./scripts/clippy_check.sh
@@ -71,19 +72,18 @@ jobs:
       - run:
           name: Code spell check
           command: ./scripts/check_spelling.sh
+      - run:
+          name: Build in release mode (for BackgroundDevnet)
+          command: cargo build --release
       - run:
           name: Save cache
           command: .circleci/scripts/cache.sh save
       - run:
           name: Cleanup old cache
           command: .circleci/scripts/cache.sh cleanup
       - run:
-          name: Unit tests
-          command: cargo test --lib --bins --no-fail-fast
-      - run:
-          name: Integration tests
-          # fails if jobs not limited; read more in https://github.com/0xSpaceShard/starknet-devnet-rs/issues/378
-          command: cargo test --jobs 9 --test '*' --no-fail-fast
+          name: Tests
+          command: cargo test --no-fail-fast
 
   binary-build:
     parameters:

.github/CONTRIBUTING.md

@@ -119,32 +119,10 @@ Run all tests using all available CPUs with:
 $ cargo test
 ```
 
-The previous command might cause your testing to die along the way due to memory issues. In that case, limiting the number of jobs helps, but depends on your machine (rule of thumb: N=6):
-
-```
-$ cargo test --jobs <N>
-```
-
 #### Benchmarking
 
 To test if your contribution presents an improvement in execution time, check out the script at `scripts/benchmark/command_stat_test.py`.
 
-##### Cargo Bench execution
-
-To run the criterion benchmarks and generate a performance report:
-
-```
-$ cargo bench
-```
-
-This command will compile the benchmarks and run them using all available CPUs on your machine. Criterion will perform multiple iterations of each benchmark to collect performance data and generate statistical analysis.
-
-Check the report created at `target/criterion/report/index.html`
-
-Criterion is highly configurable and offers various options to customise the benchmarking process. You can find more information about Criterion and its features in the [Criterion documentation](https://bheisler.github.io/criterion.rs/book/index.html).
-
-To measure and benchmark memory it is best to use external tools such as Valgrind, Leaks, etc.
-
 ### Updating OpenZeppelin contracts
 
 Tests in devnet require an erc20 contract with the `Mintable` feature, keep in mind that before the compilation process of [cairo-contracts](https://github.com/OpenZeppelin/cairo-contracts/) you need to mark the `Mintable` check box in this [wizard](https://wizard.openzeppelin.com/cairo) and copy this implementation to `/src/presets/erc20.cairo`.