-
Notifications
You must be signed in to change notification settings - Fork 0
Z0046
Duane Dieterich edited this page Feb 12, 2025
·
5 revisions
| Issue | Add New Tests from New utPLSQL V3 |
|---|---|
| Status | Open |
| Assigned | DDieterich |
| Milestone | |
| Est Hrs | |
| %Complete | |
| Labels | |
| Links | Issues Summary |
- ??? At 20:10, installation with Triggers are DDL based triggers that "allows for utPLSQL to compile utPLSQL tests while they are compiled by the database".
- At 24:00, the target of the unit test is committing transactions. This is not allowed in ut3. At 28:10, the target is modified (COMMIT is removed) so it can be tested. This is justified with the statement, "Testing is not about the application code is set in stone."
- ??? At 29:05, committed test data is removed from the database so the unit test can be run again.
- ??? At 30:00, "It is rolling back for each and every test." Use "-- %rollback(manual)" to turn off.
- ??? At 33:10, testing an entire row from a query.
- ??? At 34:55. test by comparing 2 cursors, ensures data type matching (no implicit data type conversion).
- ??? At 58:00, Use of ANYDATA.
- ??? At 1:03:40, Failed to test DBMS_OUTPUT.get_lines and explained DBMS_OUTPUT should not be used. (Everything should be API based.)
- How to better document unit testing using nested contexts.
- At 32:20, verbose error message/results along with green bar in SQL*Developer.
- At 41:40, code coverage by source line vs code block coverage in 12.2 and higher.
- At 55:05, Setup in SQL*Developer. Not yet available for VS Code.
- At 57:00, How to expose internal functions/procedures in a package?
- Don't expose just for testing
- Could have private packages?
- Could use conditional compilation?
- There is a new "accessible by" option available in Oracle 18c.
- Test Driven Development asks why can't we expose private functions?
- At 1:02:25, cursor compare functionality correctly assesses duplicate rows using hashes on each row.
- At 25:55, controlling state.
- At 33:00, input/state/output matrix (Context?).
- At 37:00, using automated tests to document functionality.
- At 38:30, which tests to automate? (Risk, Value, Cost-Efficiency, History, Change Probability).
- At 42:05, testing DML, unit testing after implementation.
(Add newest entries on top and add Date/Time and Author for each entry.)
2024-03-28 16:19:36 -05:00 DDieterich Moved back to Open
2024-03-28 15:38:42 -05:00 DDieterich Created and Moved to Backlog