-
Updated
Oct 14, 2021 - Java
testing-framework
Testing is the practice of systematically testing software to make sure it works. Testing can be iterative, and happen multiple times.
Eliminate bugs and ship with more confidence by adding these tools to your workflow.
Here are 607 public repositories matching this topic...
-
Updated
Sep 1, 2021 - JavaScript
-
Updated
Oct 8, 2021 - C++
-
Updated
Oct 6, 2021 - Python
-
Updated
Jun 7, 2021 - JavaScript
-
Updated
May 26, 2021 - Kotlin
-
Updated
Oct 14, 2021 - Python
-
Updated
Sep 19, 2021 - C#
-
Updated
Oct 9, 2021 - Python
We need a page in the docs that tell users that to mock they should use from unittest import mock
.
We should note that the mock.patch
decorators don't currently work, and that we need to use the context managers instead.
Use more flake8
Right now (in precommit.py) we only enable a few checks (E9, F63, F7, F82).
Looks like there are a lot of other useful ones in there; investigate moving to a set of blocklisted checks.
Migrate to pytest
-
Updated
Oct 12, 2021 - Python
-
Updated
Oct 10, 2021 - PLpgSQL
-
Updated
Sep 30, 2021 - C++
Right now we just use the standard C random library, but really it'd be nice if the brute force fuzzer could do consistent tests across platforms, for various purposes. We probably need our own PRNG, something like:
https://www-cs-faculty.stanford.edu/~knuth/news02.html#rng
or
https://github.com/cmcqueen/simplerandom
I'm not sure what's best. We'd like decentish quality, maybe, and d
-
Updated
Oct 14, 2021 - Scala
-
Updated
Oct 6, 2021 - Python
-
Updated
Sep 24, 2021 - Shell
-
Updated
Sep 26, 2021 - C
-
Updated
Mar 25, 2020
-
Updated
Jul 22, 2021 - Scala
-
Updated
Apr 26, 2021 - Java
-
Updated
Jun 17, 2021 - C++
-
Updated
Oct 14, 2021 - HTML
-
Updated
Oct 13, 2021 - Java
-
Updated
Oct 13, 2021 - Vim script
-
Updated
Apr 1, 2020 - Go
-
Updated
Aug 30, 2021 - Jupyter Notebook
- Wikipedia
- Wikipedia
Summary
The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a