Skip to content

Commit 1ad1406

Browse files
nbelenkovPatrickAlphaCmattaerealDicksonWu654
authored andcommitted
Addition of a Mutation Testing Section (#180)
* mutation testing section Added: - Mutation Testing Section - Reference to Mutation Testing in Unit Testing * changes based on PR feedback Co-authored-by: Patrick Collins <54278053+PatrickAlphaC@users.noreply.github.com> * Moved the evaluating test suite part to Readme * updated summary as requested * Fixing the linter to take into account subfolders as well (#191) * Fixing the linter to take into account subfolders as well * Mass fixing linting * fixing linting in justfile * Update src/external-security-reviews/README.md Co-authored-by: Dickson Wu <33645481+DicksonWu654@users.noreply.github.com> --------- Co-authored-by: Dickson Wu <33645481+DicksonWu654@users.noreply.github.com> * Update SUMMARY.md.develop --------- Co-authored-by: Patrick Collins <54278053+PatrickAlphaC@users.noreply.github.com> Co-authored-by: Matías Aereal Aeón <388605+mattaereal@users.noreply.github.com> Co-authored-by: Dickson Wu <33645481+DicksonWu654@users.noreply.github.com>
1 parent eba8314 commit 1ad1406

2 files changed

Lines changed: 2 additions & 3 deletions

File tree

docs/pages/security-testing/README.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ tags:
99
contributors:
1010
- role: wrote
1111
users: [patrickalphac, mattaereal, nbelenkov]
12-
1312
---
1413

1514
import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'
@@ -48,7 +47,6 @@ For smart contracts in particular, here is when to use each type of testing:
4847
- **Static Analysis**: Always. Use tools like [Slither](https://github.com/crytic/slither) and [Aderyn](https://github.com/Cyfrin/aderyn) to analyze the code for vulnerabilities.
4948
- **Formal Verification**: Dependent. Anywhere functions are math heavy, stateless, or functionality matches another system, this should be used.
5049

51-
5250
## Evaluating your test suite
5351

5452
To ensure you're meeting the goals of security testing, it's essential to evaluate the quality and completeness of your test suite. This can be done through several approaches:
@@ -59,4 +57,4 @@ Together, methods like these can give a more complete picture of how well your t
5957
---
6058

6159
</TagProvider>
62-
<ContributeFooter />
60+
<ContributeFooter />

docs/pages/security-testing/unit-testing.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -270,6 +270,7 @@ function testTransfer() public {
270270
}
271271
```
272272

273+
273274
## Common Smart Contract Tools and Frameworks
274275

275276
- [Foundry (Solidity)](https://github.com/foundry-rs/foundry):

0 commit comments

Comments
 (0)