Skip to main content

Oracle DB Testing with Selenium



1. For Database Verification in To use Selenium Webdriver, we need to use the JDBC ("Java Database Connectivity"). Its API provides following classes and interfaces:


  • Driver Manager
  • Connection
  • Statement
  • ResultSet
  • SQLException


2. In order to test our Database using Selenium, we need to perform the following steps:

a. Make a connection to the Database. Syntax is:
Connection DB_Con= DriverManager.getConnection(URL, "USERID", "PASSWORD" )

And load JDBC Driver class using the syntax:
Class.forName("oracle.jdbc.driver.OracleDriver");

b. Execute Queries to the Database

Statement stmt = DB_Con.createStatement();

stmt.executeQuery(select *  from employee;);

ResultSet rs= stmt.executeQuery(query);

c. Process the result set based on your need:

while (rs.next()){

String FisrtName= rs.getString(1);         
String LastName= rs.getString(2);
System.out.println("First Name is: " +FisrtName);
System.out.println("LastName is: " +LastName);
}

d. close DB connection

DB_Con.close();

Note* We should download an Oracle Jar from Oracle website like for Oracle11 (Classes12.jar) we can get it from http://www.oracle.com/technetwork/apps-tech/jdbc-10201-088211.html  and add this JAR in our project Build Path.


Sample code:

package com.qa.Util;

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;

public class ConnectDB {

public static ResultSet getData(String query, String environment) {
String JDBC_DRIVER = null;
String DB_URL = null;
String PASS = null;
String USER = null;

if (environment.equalsIgnoreCase("QA")) {
JDBC_DRIVER = "oracle.jdbc.driver.OracleDriver";
DB_URL = "jdbc:oracle:thin:@dbtest.site.com:1001:<TEST>";
PASS = "testpwd";
USER = testuser";

}

Connection conn = null;
Statement stmt = null;
ResultSet rs = null;

try {

Class.forName(JDBC_DRIVER);

conn = DriverManager.getConnection(DB_URL, USER, PASS);

stmt = conn.createStatement();

rs = stmt.executeQuery(query);

} catch (Exception e) {
e.printStackTrace();
}
return rs;
}
}





package com.qa.Util;

import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.ArrayList;
import java.util.Collection;
import java.util.List;
import java.util.TreeSet;


public class FetchDBData {


String querytoFetch = "select rcv_ser_no from testDB.activation where BOX_NUMBER like 'DEF%' and (to_char(contract_eff_dt) >= to_date('01-MAR-18') and to_char(contract_eff_dt) <= to_date('01-MAY-18')) and rownum=1";

public static String FREE_BOX;

public static String GetTSN() throws SQLException {
ResultSet rs = ConnectDB.getData(querytoFetch, "QA");
while (rs.next()) {
FREE_BOX= rs.getString("box_no");
}

return FREE_BOX;
}

}

Comments

Popular posts from this blog

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...

Stop Overengineering: Why Test IDs Beat AI-Powered Locator Intelligence for UI Automation

  We have all read the blogs. We have all seen the charts showing how Generative AI can "revolutionize" test automation by magically resolving locators, self-healing broken selectors, and interpreting UI changes on the fly. There are many articles that paints a compelling picture of a future where tests maintain themselves. Cool story. But let’s take a step back. Why are we bending over backward to make tests smart enough to deal with ever-changing DOMs when there's a simpler, far more sustainable answer staring us in the face? -             Just use Test IDs. That’s it. That’s the post. But since blogs are supposed to be more than one sentence, let’s unpack this a bit. 1. Test IDs Never Lie (or Change) Good automation is about reliability and stability. Test IDs—like data-testid ="submit-button"—are predictable. They don’t break when a developer changes the CSS class, updates the layout, or renames an element. You know...