A Good Test Case Results in a Faster Solution

 According to the IEEE Standard 610 a test case is: "A set of test inputs, execution
conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. 

Why a Test Case?

  A test case is needed for several different situations, below are a few of them:

    To find and show defects in the code.
    To show that the code conforms to standards.
    To test the usability of the code.
    To demonstrate the exact constructs of the code.

In each of these situations a minimal Test Case will help to find defects faster and it will help determine if the code conforms to the standards. A Test Case will help to solve usability and how-to questions on the products. The creative part of Development allows the developer to choose different ways of accomplishing a result. The Test Case will show the exact constructs used that resulted in the issue. Oracle Development normally requires a Test Case be submitted with the submission of a Defect on a product.

How to build a good Test Case.

  If you are advised by Oracle Support to send a Test Case for a specific issue this does not mean that you should send your complete application where you encountered the issue to Oracle Support, since these 'test cases' will provide little value in resolving the issue. Instead only provide the minimal amount of code that is absolutely necessary to reproduce your issue. Before uploading the test case, double-check that the issue is really reproduced by the test case.

Test Cases and Databases.

  If a database is involved in the Test Case, please develop the test case against the sample schemas shipped with the database, like the Scott schema or the HR/OE schema. These schemas are available and already used by Oracle for Test Cases and do not require a schema be built. This also eliminates problems with the data and schema as possible causes for the issue. The Test Case based on these schemas is very portable between Engineers that need to look at it. That reduces the time it takes to review a Test Case and start working the real issue.

  If this isn't possible for any reason, you need to provide SQL scripts to generate the appropriate objects your test case needs. In addition to that, we need SQL scripts that populate these objects with the minimal amount of data to reproduce the problem. If the problem depends on the amount of data, provide a dump file, this should however, be as minimal as possible.

Provide Test Case Instructions.

  Provide a step-by-step description on how to install the test case, what SQL scripts have to be executed, in which order and so on, and exactly how to reproduce your issue. Be as precise as possible and don't skip any steps thinking they are obvious, something obvious to you may not be obvious to someone else and will induce confusion. You will help Oracle Support a lot when you give all the information that is necessary, and you will also accelerate the handling time. Provide any third-party libraries used in the Test Case.  Also include screen images or screen recordings (Note:11.1) in the testcase among other objects when it is necessary to clarify something in more details

Create the Test Case in JDeveloper

  If possible, please create your Test Case as a JDeveloper Workspace/Project, even if it only consists of a single Java file. This allows  JDeveloper to take care of setting up the environment for the Test Case to run it.

Uploading the Test Case 

After you have gathered all files for the Test Case you have created, create one ZIP-file containing all the files and upload this ZIP-file to My Oracle Support. This is usually a zip of the application workspace in JDeveloper.

  A good Test Case will speed up and improve the handling of an issue and will help support understand the issue you are facing.

See Note How to Deliver a Testcase for JDeveloper to Oracle Software Support [ID 115336.1]

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About


This is the official blog of the Java Development Proactive Services Team. Here we will provide information on our activities, publications, product related information and more. We look forward to your feedback to improve what we do!

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
5
6
7
8
9
10
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today