- [ ] Some unit test are actually integration tests.
- [ ] Integration tests should be executed by default.
- [ ] Expensive integration tests should be moved to functionality tests and similar.
- [ ] Document this.
☐
_
Meta
- archive
- 2021-08-17-implement-fuzzy-testing.html
- 2021-08-17-implement-mutation-testing.html
- 2021-10-22-add-bit-rot-test-for-repos.html
- 2022-03-29-implement-test-recursion.html
- 2023-01-16-2-establish-uniform-code-formatting-for-Java.html
- 2023-01-29-use-standardized-build-and-test-command-for-deploy.build.at.html
- 2023-04-12-clean-up-test-tags.html
- 2023-05-14-manage-servers-via-ansible.html
- 2023-06-01-clean-up-web-server-architecture.html
- 2023-12-17-test-repo-commands.html
- 2023-12-18-refactoring-support.html
- 2023-9-10-how-to-handle-git-branches.html
- 2024-10-14-add-code-scanners.html
- 2024-10-15-consider-fault-injection.html
- 2024-10-21-fix-database-and-table-name.html
- 2024-10-29-support-behavior-driven-development.html
- 2025-01-19-provide-and-use-xsd-for-xml-of-webserver.html
- 2025-01-23-boostrap-behaviour-driven-development.html
- 2025-03-13-create-a-custom-annotation-processor-for-custom-getter-setter-generation.html
- 2025-11-23-t67-use-unified-resource-folder.html
Error Log
Back to content
ImpressumLicensingFront MenuMain MenuPrivacy PolicyUser Profile Page
Messages
Activate Javascript in order to enable all functions of this site.
Unless otherwise noted, the content of this html file is licensed under the EPL-2.0 OR GPL-2.0-or-later.
Files and other contents, which are linked to by this HTML file, have their own rulings.