My Testing Thoughts

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.p...

How to re-run your failed test cases in Cucumber with TestNG? 1. Add rerun:target/rerun.txt in your Cucumber plugin Option like: plugin = {"rerun:target/rerun.txt" } 2. Once you execute you main Runner class it will create "rerun.txt" file in "target" folder which will have your failed test cases like: OrderFlow 4:4  LoginFlow 21:21 3. You need to take this "rerun.txt" and bind it with features option of Cucumber in a new Runner class say "FailedScenarios" like: features = "@target/rerun.txt" Your TestRunner (Main) class will be like: @CucumberOptions( features = "src\\main\\java\\com\\qa\\feature", glue = { "stepDefinitions" }, plugin = { "com.cucumber.listener.ExtentCucumberFormatter:", "rerun:target/rerun.txt" }, monochrome = true, strict = true, dryRun = false, tags = { "@Regress...

How would we make sure that a page is loaded using Selenium WebDriver?                  import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.chrome.ChromeDriver; import java.util.concurrent.TimeUnit; import org.openqa.selenium.JavascriptExecutor; import org.testng.AssertJUnit; import org.testng.annotations.Test; public class CheckPageLoad { static WebDriver driver; static String pageLoadingStatus = null; @Test     void TestCase1_HomePage_LoadingCheck(){ System.setProperty("webdriver.chrome.driver","Add your chromedriver.exe path here"); driver=new ChromeDriver();   driver.manage().window().maximize(); driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); driver.get("https://postbysanta.in"); JavascriptExecutor js; js = (JavascriptExecutor) driver; String pageLoadStatus = (Str...

SMAC is a notion based on four touching technologies that create an ecosystem to enhance the IT architecture of the business. Four components of SMAC are: 1.       Social Media 2.        Mobile 3.        Analytics 4.        Cloud Social media broadens the scope of communication, Mobile connectivity allows faster communication, Analytics provide the prospect for data analysis and prediction, Cloud eliminates the geographical barriers to store information. These four concepts use different technologies. So, to learn complete SMAC you need to master all four Social Media, Mobile, Analytics and Cloud. Now in SOCIAL Media, you can learn: -  ·        Mobile marketing Mobile marketing is a multi-channel, digital marketing strategy aimed at reaching a target audience on their smartphones, tablets, and/or other mobile devic...

It’s constantly stress-free for a tester to transfer from one technology to other but at times it's additional difficult to move from one methodology to other. Jumping from custom application to COTs ( Commercial Off-The-Shelf)  is still an easy transition; tester has a better idea like what part they need to focus or which modules are more susceptible than others. When testers take up web services it tosses many challenges, it’s continuously important to know what you need to do, rather than you first do and then learn. With the dispersed architecture of loosely coupled systems which may be technically apart but frequently need to communicate in terms of data requirements. Web Services arise in the picture when such is the requirement. A Web service provides an artless interface for commutation among these loosely coupled systems using a typical data transfer mechanism. Ladders in Web service testing: The first and foremost challenge is to imagine what is expected from a...

Crowdsource testing , also identified as crowd-testing, is the exercise of sending out prototype software and app products to wide-ranging groups of people for testing rather than having testing performed internally by core QA team. It has been used to describe the process of requesting a crowd to perform a task rather than hiring consultants or contractors. It allows more entities to participate, often at a reduced cost and with enhanced testing quality. Testers may be developers or interested members of the general public, as in beta testing and they get a reward for finding software bugs. Crowdsourced product testing makes it imaginable for a larger variety of people to try a product in a superior range of conditions than what is possible in-house, often leading to glitches being found that might otherwise only be revealed by consumers. It's practically impossible to test the vast number of devices, OS and various configurations of software that applications can run on...

Introductio n When setting up an e-commerce Web site on the Internet, severe testing is vital to the implementation and maintenance of a consistent system that will create customer confidence. Testing is essential to e-commerce because e-commerce sites are both business acute and extremely visible to their users; any let-down can be immediately expensive in terms of lost revenue and even more expensive in the longer term if dissatisfied users seek substitute sites. Yet the time pressures in the e-commerce world militate against the thorough testing usually associated with business criticality, so a new methodology is needed to enable testing to be integrated into the development process and to ensure that testing does not present a noteworthy time burden. “Best practices” are constantly challenging within the context of your product, customer base, domain, layout, web design and existing online shopping conditions. The main objective of any e-commerce site ...