QA (eng)

QA terms and questions

What are different types of software testing?

Note: Except the Shakeout testing and Unit testing which are respectively done by the CMT and Coder/Developer, all other testing are done by the QA Engineer (Tester).

1) Unit testing: It is a test to check the code whether it is properly working or not as per the requirement.  It is done by the developers (Not testers).

2) Shakeout testing: This test is basically carried out to check the networking facility, database connectivity and the integration of modules. (It is done by the Configuration Team)

3) Smoke testing: It is an initial set of test to check whether the major functionalities are working or not and also to check the major breakdowns in the application. It is the preliminary test carried out by the SQA tester.

4) Functional testingal It is a test to check whether each and every functionality of that application is working as per the requirement. It is major test where 80% of the tests are done. In this test, the Test Cases are ‘executed’.

5) Integration testing: It is a test to check whether all the modules are combined together or not and working successfully as specified in the requirement

6) Regression testing: When a functionality is added to an application, we need to make sure that the newly added functionality does not break the application.  In order to make it sure, we perform a repeated testing which is called Regression Testing.  We also do regression testing after the developers fix the bugs.  See the video below for more understanding. (Courtesy of guru99.com).

7) System testing: Testing which is based on overall requirements specification and it covers all combined parts of a system. It is also a black box type of testing. System testing is black box testing, performed by the Test Team, and at the start of the system testing the complete system is configured in a controlled environment. System testing simulates real life scenarios that occur in a “simulated real life” test environment and test all functions of the system that are required in real life. Upon completion of integration testing, system testing is started. Before system testing, all unit and integration test results are reviewed by Software QA to ensure all problems have been resolved.

8) Load testing: It is a test to check the user’s response time of number of users using any one scenario (single business process) of the same application at the same time.

9) Stress testing: In this type of testing the application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand.

10) Performance testing: It is a test to check the user’s response time of number of users using multiple scenarios (multiple business process) of the same application at the same time. Continue reading

Advertisements
Standard
QA (eng)

Test Framework build 1.0

So, my latest and greatest framework build is ready (available at BickBucket, I could share the access, but it will be no core test methods, cause they came from my work and I can’t share them). This is a link to the overall description of the very first version of it. Framework available for every QA in my company and instructions, manuals, key method descriptions and examples provided, for example:

  • Which method validates that alerts and warnings exists (with expected message) and how to close them.
  • Which one method hides/shows grid columns
  • Which one method checks special characters/too long value/empty value input into the text fields
  • Which method and how add/validates date or number fields input
  • Which one method opens row menu
  • Which one validates that value exists in the grid
  • And tens of others

I successfully made TeamCity project to run test suites for some of our components and every QA could create test and upload them to the test library:

12.png Continue reading

Standard
QA (eng)

Test Suite Report Builder Comparison

Here is a short comparison of for most popular ways to build test report for TestNG + Java framework (with comparison table in the end of the post).

Log4J

This is a pretty simple logger which throws test suite execution to the Windows Console, Eclipse Console and text file.

There is no screenshot capturing or easy navigation between multiple suites, so, this is just a huge text file.

1 Continue reading

Standard
QA (eng)

Test Framework (Java, TestNG, ANT, etc)

Introduction to Automation testing:

Testing is an essential part of a software development process. While testing intermediate versions of products/projects being developed, testing team needs to execute a number of test cases. In addition, prior to release every new version, it is mandatory that the version passed through a set of “regression” and “smoke” tests. Most of all such tests are standard for every new version of product/project, and therefore can be automated in order to save human resources and time for executing them.

Benefits of using automated testing are the following:

  • Reduction of tests’ time execution and human resources required
  • Complete control over the tests’ results (“actual results” vs “expected results”)
  • Possibility to quickly change test’s preconditions and input data, and re-run the tests dynamically with multiple sets of data

Automation workflow for the application can be presented as follows:

  • First of all it is required to identify tasks that an application has to accomplish.
  • Second, a set of necessary input data has to be created.
  • Third, expected results have to be defined in order one can judge that an application (a requested feature) works correspondingly.
  • Fourth, Executes a test.
  • Finally, Compares expected results with actual results, and decides whether the test has been passed successfully.

Goal:

The goal of this framework is to create a flexible and extendable automated testing framework, which should expand test coverage for as many solutions as possible. Framework must have input and output channels and library of methods to work with UI.

Environment Specifications:

  • Selenium Webdriver. Selenium is a suite of tools for cross-platform automated testing of web applications. It runs on many browsers and operating systems and can be controlled by many programming languages and testing frameworks. Selenium WebDriver is a functional automation tool to automate the applications. It makes direct calls to the browser using each native support for automation.
  • Eclipse IDE. Eclipse is an integrated development environment (IDE) used in computer programming, and is the most widely used Java IDE. It contains a base workspace and an extensible plug-in system for customizing the environment. Eclipse is written mostly in Java and its primary use is for developing Java applications.
  • Java.
  • TestNG. Is a testing framework inspired from JUnit and NUnit. It has extended new functionalities, which made it more powerful and easier than the other testing frameworks. It supports ReportNG (simple HTML reporting plug-in) and XLST (Graphical / Pictorial reports) plug-ins to customize or extend the default TestNG reporting style. TestNG also provides ability to implement ‘IReporter’ an interface which can be implemented to generate a Customized TestNG report by users. It has ‘generateReport()’ method which will be invoked after all the suite has completed its execution and gives the report into the specified output directory.
  • Apache Ant is a Java library and command-line tool whose mission is to drive processes described in build files as targets and extension points dependent upon each other. The main known usage of Ant is the build of Java applications.
  • AutoIT Tool used to handle Windows popups for Document Uploads and Downloads.
  • Apache POI to perform operations with excel like read, write and update the excel sheet
  • Webdriver is a driver that contains programming interface for controlling all kinds of possible actions in browser.
  • Selenium TakesScreenshot to take screenshot in case of error.
  • Log4j is a reliable, fast and flexible logging framework (APIs) written in Java, which is distributed under the Apache Software License.
  • JDBC. Java Database Connectivity (JDBC) is an application programming interface (API) for the programming language Java, which defines how a client may access a database. It is part of the Java Standard Edition platform, from Oracle Corporation.

Continue reading

Standard
QA (eng)

Test Suites for Simple Chat Application (REST API)

Introduction

This is a framework with test suites which allows me to test my Simple Chat Application UI in 5 minutes.

test app

I could provide bitbucket project access upon request and this is a link to original chat application.

Short Demo

Architecure

  • TestNG and Java
  • Webdriver is a main test library
  • JDBC to work with DB (clean up test data)
  • ANT to display test results
  • Test Suites and data stores as xls files and their status updates with every run
  • Easy to use with Jenkins

Framework example to begin with

Step by step instruction how to create framework

Standard
QA (eng)

Documents generator

It’s not a secret that there are a lot of common features in a huge amount of different applications. That’s why it will be very useful to collect all this documents in one repository and make it open for everyone. At this repository analysts will be able to  collect their specifications, voting for other specifications and searching the best of them (according to previous votes of all users) for reuse.

Solving this task I see a lot of difficulties:

  1. All of my documents are confident and a have no opportunity to share them. But I have some documentation, which were created for my own ideas, and, of course, I can share them (they got only one minus – they were wrote at my native language and it’s not English).
  2. Not all of analysts ready to share their documents, because it’s the same like teaching your competitors.
  3. It could be quite hard to understand, what was wrote in each document, because each company have their own standard (in Russia everyone tries to prove, that they are working according RUP, IEEE, K. Wiegers books,…, but, as a saw, that is not true).
  4. And the last one – people are too lazy to post something, which, furthermore, connected with their job.

I decided that the first step should solve the problem of creating standardized specifications and the easiest way is to create application, which will not allow describing window/web frames in different ways (that is why I decline the idea of describing fields in Excel or Word documents).

At this point I was inspired by IBM Web Content Manager (WCM). It took about one hour to understand – how should I create web forms with amount of fields and their properties (as type, length and so on). I don’t know if it will be correct to add print screens here, but, hover, it will be easy for you to find them. So, according to WCM work process, it will be enough for analyst to specify – how/where fields should be displayed at GUI and their properties. After that, developer’s work will be decreased 2-3 times, but this is not a first step for me, and, furthermore:

  1. WCM cannot generate all of specifications, what we need at our projects.
  2. It’s too expensive while we are working only on non-portal solutions.
  3. It could work only with web frames, can’t include tables and so on.

Why I decided to made another one application on this theme

I’m educating some students (private courses) and they should understand next important things, which are easy to show on working application, which could be immediately modified:

  1. How to collect requirements
  2. How to provide impact analysis
  3. How to improve usability and make application user friendly
  4. How to work with non-functional requirements
  5. What attributes each field or table should have
  6. How to prepare a test plan for application

 Domain model

After my primary analysis of the problem – I’ll enumerate primary features for application, which will be able to generate such kind of specifications:

  1. Creating GUI description
  2. Adding fields and table parts
  3. Adding checks for input data
  4. Adding formulas for calculated fields
  5. Generating text description

This generator should be available from web or user should have an opportunity to install it on his PC without configuring database procedures. That is why it is appropriate to save all necessary data at xml-files.

Domain model:

1

In fact, I want to see many frames/GUI at project and I want to reuse one frame in other project. Then, I want each frame consist of fields (with opportunity of copying field and field’s property to another frame) and tables. Tables should consist of many frames and have their own attributes (for example, are they editable or not). And all of the verification procedures should be cross project entities.

Version 0.1

Today I made my first version, which, of course, not ready to use at my department. Nevertheless, application already has an export to XLS function and it is quite easy to understand how to work with it.

2

3

Day by day I’m planning to improve it quality and amount of useful features. I will add
description of my Frames for business analysts, rewrite dropdown lists, to make already added frames and field excluded. I have been working as analyst and QA for 6 years, so I have a complicated view on my program and all of the processes, which I’m planning to automate.

However, you will be able to download my application soon. It consists of executable JAR file and a BAT file. BAT file will help you to start my application. I didn’t want to made users install any additional software or database engines, that’s why application uses only XML files for storing information.

Standard