Skip to content

Fix nested list issue in docs #1274

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

Merged
jgebal merged 1 commit into from
Dec 6, 2023
Merged

Fix nested list issue in docs #1274

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
6 changes: 3 additions & 3 deletions docs/userguide/best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ The following are best practices we at utPLSQL have learned about PL/SQL and Uni
- Tests should not mimic / duplicate the logic of tested code
- Tests should contain zero logic (or as close to zero as possible)
- The 3A rule:
- Arrange (setup inputs/data/environment for the tested code)
- Act (execute code under test)
- Assert (validate the outcomes of the execution)
- Arrange (setup inputs/data/environment for the tested code)
- Act (execute code under test)
- Assert (validate the outcomes of the execution)
- Each tested procedure/function/trigger (code block) should have more than one test
- Each test should check only one behavior (one requirement) of the code block under test
- Tests should be maintained as thoroughly as production code
Expand Down