-
Notifications
You must be signed in to change notification settings - Fork 7
Expand file tree
/
Copy pathbuildpack.html
More file actions
66 lines (55 loc) · 3.15 KB
/
Copy pathbuildpack.html
File metadata and controls
66 lines (55 loc) · 3.15 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!-- WARNING! This file is generated. -->
<!-- To alter documentation, edit files in src directory -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Build Test Packages</title>
<link rel="stylesheet" href="utplsql.css" type="text/css" />
<meta name="keywords" content="utPLSQL, PL\SQL, Unit Testing, Framework, Oracle" />
<meta name="description" content="Unit Testing PL\SQL" />
<meta name="title" content="Build Test Packages" />
<meta name="author" content="Steven Feuerstein, Chris Rimmer, Patrick Barel and the utPLSQL Project" />
<meta name="copyright" content="(C) 2000-2005, 2014-2016 Steven Feuerstein, Chris Rimmer, Patrick Barel and the utPLSQL Project" />
</head>
<body>
<div class="purple_bar"><a href="index.html"><img src="utplsql.jpg" alt="utPLSQL logo" /></a></div>
<p>[ <a href="index.html">Home</a>
| <a href="started.html">Getting Started</a>
| <a href="buildpack.html">Build Test Packages</a>
| <a href="examples.html">Examples</a>
| <a href="userguide.html">User Guide</a>
| <a href="release.html">Release Notes</a>
| <a href="map.html">Document Map</a> ]</p>
<p><a href="admin.html">< Previous Section: Administrative Topics</a> | <a href="howto.html">Next Section: How to build a test package ></a></p>
<!-- Begin utPLSQL Body -->
<!-- $Id$ -->
<h1>Build Test Packages</h1>
<p>
We learn best by following the examples of those who have gone before
us. So you will find in this document sample test packages and different
approaches to using utPLSQL to test your PL/SQL code like it has never
been tested before!
</p>
<p>
Spend some time in the general <a href="howto.html">How to Build a Test
Package</a> so that you are comfortable with the basic steps necessary
to integrate your test code into the utPLSQL framework. The Test Run section
offers a narrative presentation of building a test package; it makes a
nice follow-up to the How To section if you still feel any uncertainty.
Then you will be more than ready to explore the <a href="examples.html">Examples</a>.
</p>
<h2><a href="howto.html">How to Build a Test Package</a></h2>
<h2><a href="testrun.html">A "Test Run" with utPLSQL</a></h2>
<!-- End utPLSQL Body -->
<p><a href="admin.html">< Previous Section: Administrative Topics</a> | <a href="howto.html">Next Section: How to build a test package ></a></p>
<div class="purple_bar"><a href="index.html"><img src="utplsql.jpg" alt="utPLSQL logo" /></a></div>
<p>
<a href="http://validator.w3.org/check?uri=referer">
<img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0 Strict" height="31" width="88" />
</a>
</p>
<p class="copyright">Copyright © 2000-2005, 2014-2016 <a href="mailto:steven@stevenfeuerstein.com">Steven Feuerstein</a>, <a href="mailto:c@24.org.uk">Chris Rimmer</a>, <a href="mailto:pbarel@vda.nl">Patrick Barel</a> and the utPLSQL Project. All rights reserved</p>
</body>
</html>