Innoviz Techonlogies | Consulting

Innoviztech

QA

Assuring the quality of an application is very important before it reaches the end user. This saves a lot of time, effort and cost. A quality product is a result of complete testing. A software project generally goes through White box testing and Black box testing and user interface testing before it reaches the user as a final product.

A capable QA team at Innoviztech can help you serve quality products by performing quality testing.

QA life cycle to assure quality

Our QA team will execute all stages of QA life cycle to assure quality of the product. Listed below are few testing types:

Black box testing

Black box testing is performed without the knowledge of the internal coding, internal paths and the execution details. Testing is purely performed based on the requirements, in which input is provided to the system and the output is checked not worrying about the internal understanding of software.

How is black box testing done?

Following are the steps carried out to perform black box testing

Examine the requirements
Prepare both positive and negative test cases based on the requirements
Execute these test cases and check for the output
Compare the actual output with the expected output.
Bugs are filed if actual output does not match with expected result
Perform retesting of fixed bugs. Also, perform regression testing to check whether the new code has not affected the existing functionality.

Black box testing is classified into three significant ones, which are as follows:

Functional testing: This relates to testing functional requirements of the software.
Non functional testing :This relates to testing non functional requirements of the software such as performance, usability and scalability.
Regression testing: Software may go through code changes, or upgrades or maintenance. This type of testing is done to check whether these changes have impacted the existing functionality.

Some of the Black boxes testing tools are as follows:

QTP and Selenium for functional testing
Load Runner and Jmeter for non functional testing

Relative to each stage of the development life cycle we have software testing life cycle (STLC)
Requirements phase: Software test manager or the testers participate during this stage of SDLC to know the requirements.
Planning and Analysis: Test plan is prepared
Design: Test cases are designed
Execution: Test cases are executed. Resolved-fixed bugs are retested. Regression testing is also performed

White box testing

White box testing, also known as clear box testing tests the internal code, design and structure of the software program. Programming knowledge is essential to perform this testing. Developers usually do this. The tester selects various inputs to be implemented through the code and decides the output. Black box testing is done from the end user perspective, while white box testing is performed depending on the internal working of the software application.
Steps to perform White Box Testing are as follows:

1. Understand source code: The tester must have the knowledge of the programming language and of security. Must be capable of detecting security issues
2. Prepare test cases and execute: Source code of the application is tested to check for the correct flow.

Test cases may not cover all the paths of the software code. Code coverage analysis is the major technique of white box testing to uncover the gaps. Thereby, test cases covering those gaps can be prepared and executed to enhance product quality.

Statement coverage: Statement coverage covers possible code statements minimum once during testing
Branch coverage: Covers all possible paths of software application

White Box testing types
Unit testing: After developing a few lines of code developer checks the functionality of the application for the code written. This helps find bugs in the early stage of software development. This saves time money and comparatively easy to fix.

Memory leaks: Memory leaks are the cause of slow running applications. An experienced tester is required to identify the memory leaks.

User interface testing

End user uses the front end of any web based applications. GUI tests the graphical user interface of the application. This checks the components such as buttons, checkboxes, Radio button, Breadcrumbs, Accordion, Carousel, icons and menu.

Why is GUI testing required?
When the user visits the website for the first time, he/she would see the look and feel of the application. Also, sees whether the website is interesting, comfortable, understandable and easy to use. Then alone the user would visit the website for next time. So, keeping this in view GUI testing is essential and significant. Ensure that the application is bug free interface before it reaches the end user.

For instance, WebPages are shown differently on different browsers. Keeping this in view, user interface should be tested to ensure that the all the pages appear aligned and managed without any distortion on various web browsers. Also, if the page has any images, they should be visible completely in all browsers. When the screen is resized they should get cropped. Buttons should work fine when clicked.
In addition, below are some of the points to test the GUI:

1. Depending on the field type, the fields must accept the values. For instance, if the field is a numeric type it has to accept only numeric values. GUI components length, width, position and size should be checked.
2. User interface should be attractive
3. Spellings should be correct
4. Font should be readable. The color should meets the standard
5. Text should be properly aligned
6. Images should be properly aligned and must be of good quality
7. All the GUI elements have to be properly aligned for various screen resolution
8. Error messages and their color should be correctly displayed
9. Session expiry should not be too short nor too long

We would love to hear about start your new project? Start New Project