Skip to content

Commit b5e4652

Browse files
authored
Week 2: Presentation proposal (samkh & atheers) (#2372)
* Create README.md * fix: add group folder inside correct week folder
1 parent 3ad49da commit b5e4652

File tree

1 file changed

+33
-0
lines changed
  • contributions/presentation/week2/samkh-atheers

1 file changed

+33
-0
lines changed
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Assignment Proposal
2+
3+
## Title
4+
5+
Property-based testing in Python using Hypothesis
6+
7+
## Names and KTH ID
8+
9+
- Sam Khosravi ([email protected])
10+
- Atheer Salim ([email protected])
11+
12+
## Deadline
13+
- Week 2
14+
15+
## Category
16+
- Presentation
17+
18+
## Description
19+
20+
We want to explain the topic of property-based testing,
21+
where the coder defines the properties that the test cases must satisfy,
22+
which then automatically generates test cases that enforce these properties.
23+
We will look at how this is done in practice in Python using Hypothesis,
24+
which is a library for creating unit tests in Python, based on property-based testing.
25+
Instead of normal example-based testing, which we have seen in school where we manually define input-output pairs,
26+
property-based testing instead tests a wider range of inputs to make sure that the code keeps true to the properties the coder has defined.
27+
28+
**Relevance**
29+
30+
Usually, example based testing is used when writing unit tests, where the programmer has to come up with various test inputs and define what the expected results are.
31+
This is tedious and error-prone in the long run, thus one can utilize property-based testing to speed up the processes.
32+
Property-based testing also explores more inputs and conditions, which makes it easier to uncover edge cases.
33+
This is relevant to DevOps as it concerns test automation as well as being able to significantly enhance the testing suite.

0 commit comments

Comments
 (0)