Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add warnings to testing section #21

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add warnings to testing section #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion episodes/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,7 +228,13 @@ An example where you would like to do this for a research project might be when

In the previous parts we have looked at quite a few different types of test with examples. Also, some ways on making the tests more reusable and improving the quality. We would like to end with giving a few more possible resources where you could find information about different types of tests or testing tools:

> ## `Warnings`
>
> We can add warnings: "if functionality has not changed, tests should not change" -- this type of comments.
{: .caution}


- [pytest and all types of integrations with it](https://pytest-with-eric.com/)
- [the turing way](https://book.the-turing-way.org/reproducible-research/testing)
- [Behaviour driven development with Gherkin syntax](https://behave.readthedocs.io/en/latest/tutorial/)
- [testing pyramid vs honeycomb testing](https://engineering.atspotify.com/2018/01/testing-of-microservices/)
- [testing pyramid vs honeycomb testing](https://engineering.atspotify.com/2018/01/testing-of-microservices/)
Loading