Pradyot Ranjan
Pradyot Ranjan
# Description Moving to a src layout is a better option overall. You can read more about it here: https://packaging.python.org/en/latest/discussions/src-layout-vs-flat-layout/#:~:text=Auto%20color%20theme-,src%20layout%20vs%20flat%20layout,-%23 It was decided internally to move to a `src` layout....
**Purpose of PR?**: This is a fuzzer for `ContainerPolicy` https://github.com/kubearmor/KubeArmor/blob/a5f584c38ee7cd674d1e95a3f7ce7842212dfe12/KubeArmor/policy/policy.go#L24 For seed corpus I referred to [this](https://docs.kubearmor.io/kubearmor/documentation/security_policy_examples#:~:text=Block%20a%20specific%20executable) policy and removed `Metadata.Name` from it. With this we are testing if invalid...
Keeping `build.sh` here for easy integration of fuzzers in future
Pytest offers various features, one of them being the use of [fixtures](https://docs.pytest.org/en/6.2.x/fixture.html). This helps us better manage the tests and setup preconditions. Using the `pytest.mark.parameterize` fixture helps us give multiple...
# Description Trying to remove contents of shared.py using pytest fixtures.
**Purpose of PR?**: Fixing bugs in fuzzers. Seed value changed from yaml to json for checking for generation of invalid json inputs. `ContainerPolicy` and `HostPolicy` now returns err for generated...
## What type of PR is this? (check all applicable) - [ ] 💾 Refactor - [x] 🪄 Feature - [ ] 🐞 Bug Fix - [ ] 🔧 Optimization...
Fixes: #739
Pybamm migrated from unittest to pytest successfully in the last GSoC cohort. See : https://pybamm.org/gsoc/2024/#migrate-from-unittest-to-pytest-and-improve-pybamms-testing-infrastructure . What now remains is implementing hypothesis for property based testing. This will ensure more...