You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Definitions.md
+26-5Lines changed: 26 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,27 @@
1
1
[Website Home Page](README.md)
2
2
3
-
# Other Definitions
3
+
# Definitions
4
+
5
+
---
6
+
## wtPLSQL Definitions
7
+
8
+
These are the working definitions for the wtPLSQL project.
9
+
10
+
**Annotation** - PL/SQL comment used to identify a DBOUT or ignore source code lines from code coverage data.
11
+
12
+
**Assertion** - A function that performs a single test and records/reports the result.
13
+
14
+
**Coverage** - An indication of the amount or percentage of source code tested.
15
+
16
+
**DBOUT** - Database Object Under Test. The database object that is the target of testing. White-box testing is oriented toward a specific DBOUT. Code coverage is also oriented toward a specific DBOUT.
17
+
18
+
**Setup** - Modifying the database or environment in preparation for an assertion, testcase, or group of either.
19
+
20
+
**Teardown** - Restoring a database or environment after an assertion, testcase, or group of either.
21
+
22
+
**Testcase** - A logical grouping of assertions to run happy path, decision tree, boundary condition, and/or fault insertion tests. May included one or more setup, teardown, and intermediate setups.
23
+
24
+
**Test Runner** - A PL/SQL package that exercises a DBOUT and uses assertions to confirm the correct funcionality of the DBOUT. It may have zero or more testcases. It always contains a call to the WTPLSQL.TEST_RUN procedure. It may contain DBOUT annotations and "ignore source lines" annotations.
4
25
5
26
---
6
27
## Oracle Database
@@ -10,7 +31,7 @@ Note: Some Oracle database terms overlap with Object Oriented terms.
10
31
11
32
**Schema** - Database owner of a database object.
12
33
13
-
***
34
+
---
14
35
## XUnit
15
36
These definitions were taken from [Xunit at Wikipedia](https://en.wikipedia.org/wiki/XUnit). They include minor editing for clarification.
16
37
@@ -33,7 +54,7 @@ The setup and teardown serve to initialize and clean up test fixtures.
33
54
34
55
**Assertions** - A function or macro that verifies the behavior (or the state) of the unit under test. Usually an assertion expresses a logical condition that is true for results expected in a correctly running system under test (SUT). Failure of an assertion typically throws an exception, aborting the execution of the current test.
35
56
36
-
***
57
+
---
37
58
## JUnit
38
59
These definitions were taken from the [JUnit Team at GitHub](https://github.com/junit-team/junit/wiki)
39
60
@@ -47,7 +68,7 @@ These definitions were taken from the [JUnit Team at GitHub](https://github.com/
47
68
48
69
**Test Fixture** - A test fixture is a fixed state of a set of objects used as a baseline for running tests. The purpose of a test fixture is to ensure that there is a well known and fixed environment in which tests are run so that results are repeatable.
49
70
50
-
***
71
+
---
51
72
## JUnit XML For Jenkins
52
73
These definitions are based around the JUnit XML for Jenkins requirement. There is some translating required as the Oracle database is relational, not object oriented. Additionally, the Jenkins XML specification has some nuances that are not obvious.
53
74
@@ -63,7 +84,7 @@ These definitions are based around the JUnit XML for Jenkins requirement. There
Copy file name to clipboardExpand all lines: docs/README.md
+14-34Lines changed: 14 additions & 34 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Use [GitHub "issues"](https://github.com/DDieterich/wtPLSQL/issues) for support.
9
9
10
10
## Example wtPLSQL Test Results
11
11
12
-
This is the summary from the WT_ASSERT package self-test. This is the default DBMS_OUTPUT format. Because test results and code coverage is stored in Oracle tables, other report formats a simple to create.
12
+
This is the summary from the WT_ASSERT package self-test. It was created with the default DBMS_OUTPUT reporting package. Because test results and code coverage is stored in Oracle tables, other report formats are simple to create.
13
13
14
14
```
15
15
wtPLSQL 1.1.0 - Run ID 7: 09-Jun-2018 11:48:42 AM
@@ -30,11 +30,7 @@ This is the summary from the WT_ASSERT package self-test. This is the default D
30
30
Trigger Source Offset: 0
31
31
```
32
32
33
-
To view the complete test results from the wtPLSQL self-test, go to the [test_allO.LST](https://github.com/DDieterich/wtPLSQL/blob/master/src/core/test_allO.LST) file in GitHub.
34
-
35
-
## Demonstrations and Examples
36
-
37
-
[Under Construction](demo/README.md)
33
+
To view the complete test results from the wtPLSQL self-test, go to the [test_allO.LST](https://github.com/DDieterich/wtPLSQL/blob/master/src/core/test_allO.LST) file in GitHub. The [Demonstrations and Examples Page](demo/README.md) has more examples.
38
34
39
35
## What is wtPLSQL?
40
36
@@ -48,27 +44,7 @@ Because all testing with wtPLSQL is for driven by custom PL/SQL packages, a [Bes
48
44
49
45
The [About wtPLSQL page](About-wtPLSQL.md) has more information about the history and testing methodology of wtPLSQL.
50
46
51
-
## wtPLSQL Definitions
52
-
53
-
These are the working definitions for the wtPLSQL project.
54
-
55
-
**Annotation** - PL/SQL comment used to identify a DBOUT or ignore source code lines from code coverage data.
56
-
57
-
**Assertion** - A function that performs a single test and records/reports the result.
58
-
59
-
**Coverage** - An indication of the amount or percentage of source code tested.
60
-
61
-
**DBOUT** - Database Object Under Test. The database object that is the target of testing. White-box testing is oriented toward a specific DBOUT. Code coverage is also oriented toward a specific DBOUT.
62
-
63
-
**Setup** - Modifying the database or environment in preparation for an assertion, testcase, or group of either.
64
-
65
-
**Teardown** - Restoring a database or environment after an assertion, testcase, or group of either.
66
-
67
-
**Testcase** - A logical grouping of assertions to run happy path, decision tree, boundary condition, and/or fault insertion tests. May included one or more setup, teardown, and intermediate setups.
68
-
69
-
**Test Runner** - A PL/SQL package that exercises a DBOUT and uses assertions to confirm the correct funcionality of the DBOUT. It may have zero or more testcases. It always contains a call to the WTPLSQL.TEST_RUN procedure. It may contain DBOUT annotations and "ignore source lines" annotations.
70
-
71
-
The [Other Definitions page](Other-Definitions.md) includes definitions from many sources to help define the terms used in various software testing methodologies.
47
+
The [Definitions page](Definitions.md) includes definitions from many sources to help define the terms used in various software testing methodologies.
72
48
73
49
## How does wtPLSQL compare to utPLSQL V3?
74
50
@@ -84,19 +60,23 @@ The goal of wtPLSQL has been to implement the basic/core functionality of utPLSQ
84
60
85
61
More information is available [in this link](utPLSQL-V2-Comparison).
0 commit comments