org.xmlBlaster.test.classtest
Class Sql92SelectorTest

java.lang.Object
  junit.framework.Assert
      junit.framework.TestCase
          org.xmlBlaster.test.classtest.Sql92SelectorTest

All Implemented Interfaces:

junit.framework.Test

public class Sql92SelectorTest
extends junit.framework.TestCase

Test ClientProperty.

All methods starting with 'test' and without arguments are invoked automatically

Invoke: java -Djava.compiler= junit.textui.TestRunner -noloading org.xmlBlaster.test.classtest.Sql92SelectorTest

See Also:

ClientProperty, The client.qos.clientProperty requirement

Field Summary

private java.util.Map[]	dataSet
protected Global	glob
private static java.util.logging.Logger	log
private static java.lang.String	ME
private java.lang.String[]	querySet
private boolean[][]	resultSet

Constructor Summary

Sql92SelectorTest(Global global, java.lang.String name)

Sql92SelectorTest(java.lang.String name)

Method Summary

private void	consistencyCheck() Checks if the provided data sets, the queries and the results are consistent with eachother (this is invoked before starting the real testing)
private java.lang.String	getDataAsText(int pos)
void	interactive()
static void	main(java.lang.String[] args) java org.xmlBlaster.test.classtest.Sql92SelectorTest
private void	performanceCheck()
private void	selectorPerformTest() This is the fully automatized initial (general) test.
protected void	setUp()
private void	setupDataSets() Change this method if you want to add a new data set to be checked
protected void	tearDown()
void	testArithmeticOps() Tests the outer logical operators AND, OR, NOT with and without brackets.
void	testBetweenOps() Tests the IN (...) statements.
void	testInSetOps() Tests the IN (...) statements.
void	testLikeOps() Tests the LIKE statements.
void	testLikeOpWrapper() These are the examples found in the JMS 1.1.
void	testLogicalOps() Tests the outer logical operators AND, OR, NOT with and without brackets.
void	testNullOps() Tests the NULL and NOT NULL statements.
void	testRegexOps() Tests the REGEX statements.

Methods inherited from class junit.framework.TestCase

countTestCases, createResult, getName, run, run, runBare, runTest, setName, toString

Methods inherited from class junit.framework.Assert

assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, fail, fail

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Field Detail

ME

private static final java.lang.String ME

See Also:

Constant Field Values

glob

protected Global glob

log

private static java.util.logging.Logger log

dataSet

private java.util.Map[] dataSet

resultSet

private boolean[][] resultSet

querySet

private java.lang.String[] querySet

Constructor Detail

Sql92SelectorTest

public Sql92SelectorTest(java.lang.String name)

Sql92SelectorTest

public Sql92SelectorTest(Global global,
                         java.lang.String name)

Method Detail

setUp

protected void setUp()

Overrides:

setUp in class junit.framework.TestCase

tearDown

protected void tearDown()

Overrides:

tearDown in class junit.framework.TestCase

setupDataSets

private void setupDataSets()

Change this method if you want to add a new data set to be checked

consistencyCheck

private void consistencyCheck()

Checks if the provided data sets, the queries and the results are consistent with eachother (this is invoked before starting the real testing)

getDataAsText

private java.lang.String getDataAsText(int pos)

selectorPerformTest

private void selectorPerformTest()

This is the fully automatized initial (general) test. Since it is difficult to predict all possible problems, additional tests should be added once a bug is encountered. For each such bug an own test method should be added.

performanceCheck

private void performanceCheck()

interactive

public void interactive()

testLogicalOps

public void testLogicalOps()

Tests the outer logical operators AND, OR, NOT with and without brackets. For each data there must be a boolean value telling if the result is true or false

testNullOps

public void testNullOps()

Tests the NULL and NOT NULL statements. For each data there must be a boolean value telling if the result is true or false

testArithmeticOps

public void testArithmeticOps()

Tests the outer logical operators AND, OR, NOT with and without brackets. For each data there must be a boolean value telling if the result is true or false

testInSetOps

public void testInSetOps()

Tests the IN (...) statements. For each data there must be a boolean value telling if the result is true or false

testBetweenOps

public void testBetweenOps()

Tests the IN (...) statements. For each data there must be a boolean value telling if the result is true or false

testLikeOps

public void testLikeOps()

Tests the LIKE statements. For each data there must be a boolean value telling if the result is true or false

testRegexOps

public void testRegexOps()

Tests the REGEX statements. For each data there must be a boolean value telling if the result is true or false

testLikeOpWrapper

public void testLikeOpWrapper()

These are the examples found in the JMS 1.1. specification

main

public static void main(java.lang.String[] args)

  java org.xmlBlaster.test.classtest.Sql92SelectorTest