|
|
Category:
Best Practices
Sub-Categories:
0,
Documents:
8,
Last Update:
Aug 27, 2009 8:32 AM
|
|
Documents in Category
|
|
|
|
Testing attributes of object types
[2439]
Last Modified:
Nov 30, 2008 10:23 AM
Code Tester does not yet allow you to natively/automatically test attributes of object types returned by programs. You can, however, use an Expression test type to test individual attributes. This document describes the process.
|
|
|
|
Testing private subprograms of a package
[2001]
Last Modified:
Aug 27, 2009 8:32 AM
************************************
NOTE: In 1.8.3 and 1.8.4, the advice
given in this document will NOT WORK.
We hope to have it fixed in 1.9, but
in the meantime, if you want to test
private programs, you must expose
|
|
|
|
Version Control software and Code Tester
[1922]
Last Modified:
May 29, 2008 2:09 PM
A common question regarding Code Tester is how it integrates with version control software. More generally, it is important to know how and what one should considering storing in a version control repository.
This document explores this
|
|
|
|
Testing and refreshing data from production
[1872]
Last Modified:
Apr 29, 2008 2:18 PM
In the process of talking about Code Tester with many developers, I have come across a belief regarding code testing and the refreshing of data from production tables that I think actually reflects a misunderstanding about both how to use Code Tester specifically and, more generally, how to test our code.
Here's the way this belief was expressed by a customer recently:
"We have a development environment - let's call it TEST. Inside this environment is the supporting schema / repository for Code Tester, as well as the test definitions and generated test code.
"Once a week, we refresh the TEST environment from the production environment, PROD. PROD doesn't contain a Code Tester repository, so after I refresh, I lose my test repository and code."
The attached document explores the challenges of testing when you refresh from production, and why you might not want to do that for functionality testing.
|
|
|
|
Using Quest Code Tester with a Centralized Code Schema
[1871]
Last Modified:
Apr 29, 2008 11:07 AM
This zip file contains a Word doc that explains how in 1.8.1 you can use a backend API call in the my_codetester package to use Code Tester with a centralized code schema (summary: you need to tell Code Tester to include the AUTHID CURRENT_USER
|
|
|
|
Use my_commit to avoid hard-coded commits in your application code
[841]
Last Modified:
Oct 4, 2007 5:53 PM
If you call commit; directly in your code, then you will save changes made to your tables, which can disrupt other test cases that you are running. You should install call my_commit.perform_commit; and then when you are testing your code, simply call my_commit.turn_off; in your initialization section. This will disable commits for that session.
|
|
|
|
Make Code Tester available to a specific schema (private synonyms)
[772]
Last Modified:
Oct 4, 2007 5:53 PM
Use the attached scripts to grant access to Code Tster from a specific schema, and to create private synonyms on Code Tester objects in that schema.
|
|
|
|
Six Simple Steps to Unit Testing Happiness
[333]
Last Modified:
Oct 4, 2007 5:54 PM
This powerpoint presentation explores the negative effect of bugs and introduces test-driven development as a process for reducing bugs.
|
|
|
|
|
|
|
