• Introduction
• Manual testing
• Autoit
• Ant
• Agilitest
• Bat
• Bat With Params
• Beanshell
• Cerberus
• Cucumber
• Cucumber v2 (BDD & Gherkin support)
• eTASQ Motion (Ponant)
• Executable
• FitNesse
• Gatling
• Generic Version-Control
• Git, Gitlab, Github
• Gradle
• Java
• Jar
• JMeter
• JMeter SQL
• JMeter Web
• JUnit
• Katalon
• Katalon v2
• Marathon
• Maven
• Mocha
• NeoLoad
• NUnit
• Odin Axe
• Odin Axe Results
• Offline
• Perl
• PHPUnit
• Postman (Newman)
• Protractor
• Python
• PyUnit
• PyTest
• QF-Test
• Quick Test Pro/UFT
• Ranorex
• Rapise
• RobotFramework
• RobotFramework v2
• RobotFramework v3
• RobotFramework v4
• Sahi
• Sahi 3.5
• Sahi 4.0
• Sahi 6.0
• Selenese
• Selenium HTML
• Selenium 3
• Selenium Java
• Selenium .NET
• Selenium Python
• Shell
• Sikuli
• SikuliX
• SilkTest
• SoapUI
• SoapUI Load
• SoapUI Security
• SOATest
• SQL Compare
• SQL Select
• Squish
• SVN (Subversion)
• Tape
• Tcl
• TestComplete
• TestComplete v2
• TestExecute
• TestExecute v2
• TestNG
• TestOptimal
• TestOptimal Simple
• TestPartner
• TestStand
• VisualStudio
• VisualStudio Coded UI
• WAPT
• WebdriverIO
• WebUI
• XCI
• xUnit.net
• Success (skeleton)
• Random (skeleton)
• Proxy

SQL Compare Launcher (sql_compare.jar)

Configuration

Process

• If necessary, connect to a remote host using plink with specific credentials (in the configuration) and execute the command specified (as well in the configuration)
• Establish 2 separate connections to the databases specified in the configuration
• Execute the sql script <sqlScriptRootPath>/<testPath>/<testName>_<testcaseName>_a.sql on the first database
• Execute the sql script <sqlScriptRootPath>/<testPath>/<testName>_<testcaseName>_b.sql on the second one
• Compare both result sets

Tutorial: Creating and executing SQL Compare tests

Prerequisites

CREATE TABLE table_stock_1 (
  article_id INTEGER,
  article_name TEXT,
  article_color TEXT,
  article_nb INTEGER,
  PRIMARY KEY(article_id)
);

INSERT INTO table_stock_1 VALUES
(1, 'Hat', 'Red', 10),
(2, 'Hat', 'Blue', 4),
(3, 'Hat', 'Green', 17),
(4, 'Sweat-shirt', 'Red', 5);

CREATE TABLE table_stock_2 (
  article_id INTEGER,
  article_name TEXT,
  article_color TEXT,
  article_nb INTEGER,
  PRIMARY KEY(article_id)
);

INSERT INTO table_stock_2 VALUES
(1, 'Hat', 'Red', 10),
(2, 'Hat', 'Blue', 4),
(3, 'Hat', 'Green', 17),
(4, 'Sweat-shirt', 'Red', 5);

CREATE TABLE table_stock_3 (
  article_id INTEGER,
  article_name TEXT,
  article_color TEXT,
  article_nb INTEGER,
  PRIMARY KEY(article_id)
);

INSERT INTO table_stock_3 VALUES
(1, 'Hat', 'Red', 10),
(2, 'Hat', 'Blue', 3),
(4, 'Sweat-shirt', 'Red', 6);

• Create the text file C:\\test_repository\\tests\\sql_compare\\folder1\\test1_testcase1_a.sql and write in it:
  SELECT * FROM table_stock_1;
• Create the text file C:\\test_repository\\tests\\sql_compare\\folder1\\test1_testcase1_b.sql and write in it:
  SELECT * FROM table_stock_2;

• Create the text file C:\\test_repository\\tests\\sql_compare\\folder1\\test1_testcase2_a.sql and write in it:
  SELECT * FROM table_stock_1;
• Create the text file C:\\test_repository\\tests\\sql_compare\\folder1\\test1_testcase2_b.sql and write in it:
  SELECT * FROM table_stock_3;

Create a dedicated category for SQL Compare tests and create a test

• create a category SQL Compare associated to the launcher sql_compare.jar
• under this category, create (somewhere in the tree) a test with name test1 and with a canonical path set to folder1.
• create 2 test cases under this test named testcase1 and testcase1 (this is what is used to find the right script on disk).

Creating a test campaign

• create a campaign including only the test test1
• create a campaign session specifying in the configuration:
  • sql scripts root path: C:/test_repository/tests/sql_compare
  • the same driver, classpath and credential to connect to the test database (connection 1 and 2)

Run a campaign session

Permissions

Debug