Jmeter Tutorial: Learn about the tool in a jiffy!

Posted on July 6, 2020 by tbsupadminnxtbackendacc

Jmeter Tutorial blog by us will help you in learning about the famous tool and what’s it is used for. Usually, Apache JMeter is used for performance testing. Performance testing is one of the important testings to be performed on AUT. It will let you know the load which your application can handle and what happens if that load exceeds prescribed limits.
Through, meter tutorial let us know more about JMeter and see how it can be used for performance testing.

About JMeter – Jmeter tutorial introduction
JMeter is an open-source software which is designed by Apache Foundation. It is used to apply load to AUT to know its performance. With the help of JMeter, you will be able to apply a heavy load to the application with concurrent or multiple traffic to emulate real-time user behavior.
For applications such as Amazon who release flash day sales, it is very important to do performance testing. On a single day and in a time interval of 5 mins many customers hit the site and we must make sure that the application behaves expectedly without any flaws. One more application where performance testing is very important is the railway ticket booking website where a large chunk of people hit the server at the same time. In these cases, it becomes very necessary to test out the website under heavy load.
JMeter is usually used for testing of web or FTP application. With JMeter, you will able to identify how many concurrent users a server can handle. Thinking of hitting Amazon with 1000 concurrent users. For achieving the scenario, you cannot purchase 1000 machines to achieve the behavior. JMeter allows you to hit the Amazons server with 1000 requests concurrently. JMeter simulated real-time user’s behavior intelligently. JMeter sends requests to the target server and then retrieves the statistical information of the server. With this information, it generates test reports in different formats.
Some benefits which you gain via JMeter is a User-friendly GUI, Graphical Test Results, easy installation, and platform independence. It has an amazing record and playback feature which makes it very easy to learn even for the novice. Also, its script test can be integrated with Selenium tests and beach shells for more robust automated testing. Through the Jmeter tutorial, we are trying to et up a tutorial for people to learn about this magnificent tool.

Step-by-step Jmeter tutorial

How to Download and Install Apache JMeter
JMeter is a java application and it needs Java in the machine so that it can run seamlessly. JMeter can be installed in Windows, Linux, Ubuntu, and Mac operating systems. Before installing JMeter, make sure that you have Java installed in your machine. You can check by hitting the command in your terminal. java -version
If java version is highlighted then java is installed in your system and if nothing appears then install Java by clicking here.

Now it is the time to download JMeter. Download the latest version by clicking here. Download the binary file shown below.

2. The installation of JMeter is very easy. The download binary file must be unzipped into the folder where you want to download JMeter. The unzipped folder would like just as below snapshot.

3. Run JMeter in GUI mode by clicking on the bin folder and then jmeter.bat file.

4. After clicking, JMeter will open just as below.

More on Thread Group, Samplers, Listeners and Configuration of JMeter

Thread Group is basically the application of multiple threads to AUT. Each thread represents one user who is accessing the application. With the help of the thread group, you can apply a number of threads which is defined by you.

Samplers allow JMeter to support testing of different protocols such as HTTP, FTP, JDBC, and others.

FTP Request: If you want to do performance testing for the FTP server then you can use the config element of the FTP request. You can send a download a file or upload a file request to the FTP server. You need to add parameters to the sampler such as server name, remote file name (to be downloaded or uploaded), port number, username, and password.

HTTP request

With this help of the HTTP request sampler, you can request an HTTP request to the server. With the help of this request, you can retrieve HTML files and images from the server.

JDBC request

With this help of a JDBC request sampler, you can perform database performance testing. You will be able to send a JDBC request to the server. You should be able to add the SQL query in the query tag.

SMTP Server

If you want to test the mail server then you must use the SMTP server sampler. With this protocol, we can send emails.

CSV Data set Config

If you want to test the website with different users who are having different credentials, you must take the help of CSV data set the config to pass the credentials. You can store the credentials in the text file. It will read lines from the file using a delimiter.
You must pass the data in a text file the same as the below snapshot.

HTTP Cookie Manager

When you log in to some website then your browser stores cookie so that you do not have to login again and again. Similarly, an HTTP cookie manager also does the same task for you. If the website is returning cookie in response, then it will save a cookie for you to maintain a session. You can add an HTTP cookie manager in your test plan with the help of the config element. When you will record sessions using Blaze meter, it will automatically record cookies in the HTTP cookie manager.

Listeners

Listeners listen to the results fetched by the JMeter and let you analyze the results with the help of visual reports.

View Results Tree: You get to see all the user requests in HTML format using view results listener.

Aggregate Reports

With the help of aggregate reports, you can get total samples, average, median, minimum, maximum, and throughput.

Jmeter Timers

Once you start sending requests to your AUT, you should have timers between each request so that it can simulate real-time behavior and the server does not get confused with so many requests hitting the server. Let us see the different kinds of timers which we can integrate to simulate real-time behavior.

Constant Timer

It delays each request by the same amount of time.

Gaussian Random Timer

It delays each request by any random amount of time. You can define the deviation around which the delays would be adjusted. Also, offset can be added with the gaussian distribution of deviation value and then the total delay time can be calculated.

How to do load testing with Apache Jmeter? Click here

Uniform Random Timer

It also delays each request by a random amount of time. You can define the random delay maximum time and the offset value which will be added to the random value.

Bean shell, BSF and JSR223 timers

Bean shell timers introduce a delay time between each request using bean shell scripting. BSF timer is used to add a delay time between each request using BSF scripting language. Similarly, JSR223 adds a time delay using the JSR223 scripting language.
The most used timers are constant and gaussian timers.
Assertions in JMeter
Assertions are very useful in any kind of testing as verification and validation are the heart of testing. You must compare the results with the expected results to know if we are getting the correct response or not. Let us have a look at the most common types of assertions.

Response assertion

It allows you to check the response against pattern strings. Take an example of Amazon.com. If you hit the server with some product then the response list should contain the product mentioned in the search list given in the request payload.
You can choose text response and add the test which you want to validate. I have added the text in patterns to test.

Also, we can validate the status code with the response assertion Select the field to test as response code and mention the code in the patterns to test.

Duration Assertion

It tests that the server’s response is received time limits. If it is taking more than the time mentioned, then the assertion will be failed.

Size Assertion

It checks the response has the expected number of bytes contained in it. If it is above the defined limit, then assertion will be failed. In the below snapshot, if the response has equal or less than 5000 bytes then the assertion will be passed.

XML and HTML Assertion

XML assertion verifies that the response data has correct XML syntax while HTML assertion verifies that the HTML syntax of response is correct.
Controllers in JMeter
Controllers are used in JMeter to handle requests in an organized manner. There are different kinds of controllers that can be integrated with the JMeter Test Plan. These controllers let you handle the order of requests to be sent to the server. Let us have a look at different kinds of controllers.

Recording Controller

JMeter will record your testing steps but for storing them in a container you require a recording controller.

Simple Controller

Simpler Controller is just a container to store your requests. You can give a meaningful name to the controller. In this way, if you want to duplicate the requests, you can simply add the simple controller without again and again adding so many requests. It is just for clubbing requests and in the view, results graph you will not see any controller name.

Loop Controller

It allows the requests to run a specified number of times or forever if the number has not been defined.

Transaction Controller

The transaction controller is similar to the simple controller which records the overall time for the requests to finish. It has an additional benefit over simple controller as you will be able to see the controller name which has the clubbed requests instead of individual requests name in view results graph.

Module Controller

It is based on the idea of modularity which says that a set of requests can be clubbed in a simple or transaction controller. A module controller can be used to add any set of requests by selecting the controller. Suppose if you have 3 simple controllers named login, search and logout, then with the module container you will be able to select which you want to simulate again so that you don’t have to add the same requests again and again.

Interleave Controller

This controller pickups one sampler per iteration and it is executed from top to bottom. In the below snapshot, we are having one interleave controller having 3 samplers names News Page and FAQ Page and Gump Page. It is running with 2 threads and a loop count of 5. So, a total of 10 requests will be executed per thread.

Runtime Controller

This controller controls the execution of its samplers for the given time. If you specify the run time as 10 seconds, then JMeter will run your tests for 10 seconds.

Random Controller

It is the same as the Interleave controller but instead of running from top to bottom, the random controller picks any requests randomly.

If Controller

It runs the requests only when a set of conditions is fulfilled.

Processor in JMeter
Processors are used for modifying the samplers. There are two types of processors.

Pre-processor are the processors which are applied before sampler requests. If you want JMeter to check all the links on the page and then retrieve the HTML. You can add HTML link parser which will parse links before a request is made to the server.
Post-Processor: If the request is made to the server and is the requests send you an error then the post-processor should stop the further execution.

In the above snapshot, if you choose Stop Test Now. This will stop the test if there will be any error in the response.
There is one more post-processor named debug processor which tracks the values of variables that are in the requests.

Jmeter Distributed (Remote) Testing
It is used to do testing on multiple systems. Applying all the load on a single server is not appropriate and can bring unexpected results. It is good to perform distributed testing with master-slave architecture.         There will be one master who will be driving various clients which will be again JMeter servers which will be putting load to the application under test. The firewall should be switched off in all the machines as it can block the traffic. All machines should share the sub-network and the JMeter version should be kept the same in all the machines to avoid any kind of complexities.

Steps to setup master-slave architecture (Jmeter tutorial bonus)
1.       Go to the slave server and then go to the bin directory where JMeter is downloaded. You must then execute a file named JMeter-server.bat. Suppose the slave machine has IP address 120.178.0.9.
2.       Now, go to the master machine and go to the bin directory. There, you have to edit JMeter.properties file. You must add the IP of the slave machine in front of remote_hosts.
3.       Now for running the tests, you must go to the GUI of JMeter. Select the Run section on the menu bar of JMeter and then select a remote start and then the IP address of the slave machine.

Detailed Steps to Use JMeter for Performance & Load Testing (Jmeter tutorial exclusive)
1.       Start JMeter.
2.       Add the BlazeMeter extension to the google chrome browser. Now hit the URL on the google chrome browser and record the flow with BlazeMeter. Once the steps have been captured then you can download the file from BlazeMeter in JMX extension.
3.       You can then open the JMX file in your JMeter. It will appear as below.

4. Now, you must add a number of threads, ramp-up periods, and loop count. Number of Threads is the total number of users accessing the website. The number of times per thread will execute. Ramp-up period is the delay that should be applied before starting the next user. Suppose if you have 1000 users and a ramp period of 1000 seconds then delay between every user request will be 1000/1000 = 1 second.

5. Now, add the listeners to view the graphical results. Let us add the most used listeners such as View Results and Assertions Results.

6. You can also name the requests in different transaction controllers such as login can go to login controller, authenticate, and secure to security controller and logout to sign off the controller. If you want to execute extensive tests, then these controllers will help you running many requests.
7. Add Post-processor which would stop the tests in case you get any errors in the response.

8. Add Constant timer with a time period of 300 ms between each user request.

9. For each request, you can add assertions to validate that if the requests are giving proper response. Different Response assertions can be used to validate the status code as 200 and to validate the test in the output response. You can also add duration assertion to check if the requests are completed in a particular amount of time. Size assertion can be used to check the response in bytes.

10. Now, run the tests using the green run button on top. Now it’s time to analyze view results and assertion results.

You have to analyze the throughput and deviation. Throughput is the server’s ability to handle a number of requests per minute. The higher the throughput the higher is the capacity of the server to handle user requests. The deviation is the second parameter which is of utmost importance in this graph to be analyzed. It means the variation from the average. Throughput should be higher, and deviation should be least. These parameters, you will be getting from the client which you have to validate and send a report to the client with these graphs.
Also, you must remember in this Jmeter tutorial, is the Assertion report.
You will see the different assertions been passed and failed in this tree so that you can know which ones are failing.
One more important listener is the View Results Tree listener. You will be seeing which requests got passed and which ones got failed. The ones which are in green color are passed and the ones which are in red color are failed.
The last important listener which you can add is the Summary report which will let you know total samples, average, Min, Max, Error %, Deviation, and Throughput. This report is of the utmost importance to stakeholders. Let us see how it looks.
Conclusion for Jmeter Tutorial
That sums Use JMeter tutorial to use performance and load testing so that your application is robust and can sand load without giving unexpected results. Use the wonderful elements of JMeter to share excellent reports with the stakeholders.
Hope you are satisfied with our Apache Jmeter tutorial. Please get back to us if you have any suggestions

21 Best API Testing Tools That are insanely good –

Posted on June 16, 2020 by tbsupadminnxtbackendacc

API testing tools, the right strategies, and processes have become cardinal when it comes to software development and CI/CD workflow nowadays. Before we get into the details of API testing tools let’s have at the process in a concise manner.
What is an API?
API or application programming interface is a set of tools, rules, and protocols that help in developing a software application. An API also defines how various components of software should interact with each other.
Why API testing is needed?

Investigating an app at API level would be catastrophic so it’s better to do it at first
Core functionalities of the API can be validated
Consumes less time than that of GUI functional testing
Test data is mostly derived as JSON or XML. So the process, not language dependant
Can be easily integrated with GUI testing

What is API testing in software testing?
Testing API becomes a much-needed part of the complete software ware testing. It forms the second layer of testing and requires almost 20% of testing efforts. Since there is no GUI, API testing is done at the message level. It includes testing the REST API’s, and soap web services. These APIs can be sent over HTTP, JMS, HTTPs, and MQ.

Because of API testing characteristics, it cannot be done manually, and hence there arises a need for various API testing tools for automated API testing. Various testing is done during API testing are security testing, functionality testing, load testing, reliability testing, API documentation testing, and proficiency testing.
Wish to know about the app testing process? Click here
Here let’s have a look at some of the top API testing tools for the year 2020.

ReadyAPI

ReadyAPI is a popular API testing tool by Smartbear. Some of its prominent features are:

It assists in functional, security, and load testing of RESTFUL, SOAP, GRAPHQL, and other web services.
Ensure complete quality checks for all the web services.
It is a four in one tool assimilating API performance testing, API functional testing, API & web virtualization, and API security testing.
Supports integration of API testing with CI/CD pipeline.
Supports command-line
Supports the creation of comprehensive functional API tests and data-driven functional API tests.
Removes dependencies.
Native support for DOCKER, GIT, AZURE, JENKINS, etc.
Parallel execution of functional tests and job queuing.

AcceIQ

AcceIQ is a cloud-based continuous testing podium for API automation testing. It assists in API testing without even writing a single code. It helps in automating various testing stages like test design, planning, test generation, and execution. Some of the features of AcceIQ are:

Dynamic environment management
Simplified API automation testing
Supports chain API tests for complete testing
API test planning, test case management, execution and tracking governance
Requirements tracking is interrelated with business processes
Defect tracking
Enhanced regression suite planning
Execution tracking
Seamless CI/CD and JIRA/ALM integration
Links business process with matching API
Extendable framework
No vendor lock,
Open-source aligned

Katalon studio

It is free to use, API automation testing tool. It is an all-inclusive automation tool providing solutions to the testers.
Some of its features are:

Support for both SOAP and REST API
All-inclusive API automation support
Data-driven approach.
Supports both automated and exploratory testing
AssertJ compatible
Support CI/CD integration.
Easy to use even for non-techies

RoboHydra server

It is perfect API testing tools for the users who don’t have a server but requires one. Some of its prominent features are:

Allows connecting clients-under-test to it and run the tests.
It is very versatile
Can test any HTTP, Https, or WebSockets client.
Can manage GUIs for mobile applications, public API, and complex java-based programs.
Supports exploratory testing and debugging
Ability to reverse proxy requests, increasing its utility considerably.

SoupUI

SoapUI is a famous API testing tool for functional testing. It allows the automation testing of soap, rest APIs, and web services. SoupUI comes as a free version and a pro version, pro version offering more features than the free version. Some of the features of both of them are mentioned below:
Free package:

It allows access to full source code and to create their preferred features.
Quick and easy creation of tests using drag and drop, point-and-click
Scripts can be reused.

Pro package:

Powerful data-driven testing
Support CI/CD integrations
Supports asynchronous testing

Postman

One o f the most preferred API automation testing tool. It is best for the testers who want to evade coding in IDE using development language. Its features are:

Easy-to-use
Rich interface
Supports both automated and exploratory testing
Supports mac, windows, LINUX & chrome apps
Supports swagger & RAML formats
Offers run, test, document and monitoring features
Easy knowledge sharing
Support for GRAPHQL request and GRAPHQL variables, schemas, and GRAPHQL query auto-completion function.

Tricentis Tosca

Tricentis Tosca is API testing tool for agile and DevOps. Some of its prominent features are:

Supports various protocols: AMQP, HTTP(S) JMS, RABBIT MQ, IBM MQ, SOAP, TIBCO EMS, REST, NET TCP
Maximize reuse
Integrates with AGILE and DevOps cycle
Sustainable automation
API testing on mobile, packaged apps, cross-browser, etc…
Reduced regression testing timing

Apigee

Apigee is an award-winning cross-cloud API testing tool. It allows us to measure and test API performance. Its important features are:

It is powered by JAVA script
It is multi-step.
Supports design monitor, deploy, and scale APIs
Identify performance issues
Easily create API proxies
Deploy API proxies in the cloud
Supports cloud, on-premise, or hybrid deployment model
It is useful for digital business, and the data-rich mobile-driven APIs
It is secure,
Self-healing with Apigee-Monit,
Virtual host management

Jmeter

Jmeter though was created for load testing, it also supports functional API testing. Some of its prominent features are:

Replay test results
Supports CSV files
Integration between Jmeter and Jenkins
Supports both static and dynamic resources performance testing

Rest-assured

It is a java domain-specific language tool. It is used for testing rest API services. It is bundled with many features, permitting users to continue testing without much coding. Let’s have a look at some of its features:

Integration with serenity automation framework
Supports BDD
Requires only native knowledge of HTTP
Supports apache johnson
OSGi support.
It is an open-source tool

Assertible

Features of Assertile are,

Supports continuous integration and delivery pipeline.
Integration with Slack, GitHub, and Zapier.
Validates HTTP responses
Offers sync features that automatically update tests with every change in API.
Supports encrypted variables that enhance API testing security practices.

Karate DSL

Karate DSL is an API testing tool that’s perfect for BDD methodology. Features of Karate DSL includes,

Quicker API testing
Build on cucumber-JVM
It helps in the creation of scenarios for API-based BDD tests easily.
Runs java project
No java knowledge required to write tests
Even non-programmers can write tests easily using karate DSL
It is open source

Airborne

If you are a ruby API developer, airborne can be your perfect API testing partner. Some of its most inviting features are:

It is an open-source API automation test tool
Compatible with rack- and rails-based applications.
It is developed in ruby and RSPEC
It has no user interface of its own
Have wrappers to simplify calls
Ability to reuse parts of API calls.
Requires users to learn a few important methods and basics of RUBY and RSPEC
May important features for the API framework.
Allows to prolong and generate assertions, and chaining

Swagger

Swagger is an API testing tool for functional, security, and performance testing. Some of its features are:

Easy to quick creation, management, and execution of API tests.
Capability to inspect API request-responses,
Easy validation of schema rules
Automatically generate assertions
Complex load scenarios generation
Support services from REST, SOAP to Graphql
Open-source

Fiddler

Fiddler is another prominent API testing tool. Some of its features are:

Users can monitor, modify, and recover HTTP requests.
Supports HTTP caching and compression
Detects bottlenecks in the website
Perfect for layman testers to proficient testers
Log and debug HTTP traffic
Supports security testing.

Webinject

Webinject is one of the trusted API testing tools. Some of its prominent features are:

Creates fully automated test suites for functional, regression, and acceptance testing.
Allows testing of all applications with HTTP interface, including CGI, JSP, AJAX, SOAP, SERVLETS, REST, AND XML web services.
Collects and analyses result to prepare an automated report.
It also acts as a test runner.
It can function on different platforms using PERL interpretation.

Wish to know about the talk of the town when it comes to programming languages? Click here!

HttpMaster express

HttpMaster express is a renowned name among API testing tools. Some of its main features you can count upon are:

Supports testing of rest-based web services,
Monitors API responses
Efficient command-line interface
Supports request data builder and response data-viewer
HTTPMASTER offers the standard rest methods
Also offers custom verbs, defined global parameters
Supports customized API requests
Integration with dynamic data with their requests.
Compatible with swagger

Rest console

Rest console is a perfect API testing tool for building, debugging, and testing. Some of its features are:

It is a rest-based HTTP client visualizer and constructor
Intuitive interface
Easy identification of errors.
Support basic, plain, and OAuth validation,
Customizable interface
Allows users to develop customized headers
Supports auto-complete feature.
Flexible authentication protocols
Supports custom authentication.
Easy keyboard navigation and shortcuts

Restsharp

With full .net compatibility, Rest Sharp is one of the best API testing tool. Some of the features that make it one of the best API testing tools are:

Supports exhaustive testing.
Easy application creation
Streamlined interface
Free-to-use HTTP client library
Supports post, get, patch, put, options, head, and delete operations.
It is intuitive
Easy to use and install,
Supports serialization and deserialization support synchronous and asynchronous requests.
Support analysis of XML and JSON.
Supports uploading files and forms in multiple parts.
Supports validation protocols like basic, OAUTH1, NLTM, OAUTH2, and parameter-based authentication.

PyRestTest

Another efficient tool used for mac based and LINUX based systems is. Some of its common features you can count upon are:

Easy to use
It supports YAML or JSON.
It is written in Python
Can support many add-ons.
Ideal for smoke-tests
Can create full test scenarios,
Deploys on-server quickly
Good for system health-checks.
Supports creation, extraction, and validation tools.
For a failed scenario it returns an exit code, which can be converted into parseable logs.

Unirest

Unirest is a library of almost every HTTP request client. Hence it is one of the highly preferred API automation testing tools. Some of its prominent features are:

Support for major programming languages: NODE, PYTHON, RUBY, OBJECTIVE-C, PHP, .NET, AND JAVA.
Includes a documentation page for reference
Unirest can combine with XUNIT or BDD runner
Includes code snips

Conclusion
There are various API testing tools available in the market offering various different features. Though some of the basic features are common. Your best pick will depend on your requirements.
Study your project requirements and API testing tools features in detail and figure out the best API testing tool for yourself.

How to test a taxi booking app like Uber?

Posted on May 13, 2020 by tbsupadminnxtbackendacc

How to test a taxi booking app like Uber? They are extremely complex and demand high data security. On the top, they have to offer unvarying stability and high UX. If you are thinking about testing. you need assistance from someone who knows what they do.
However, some might be thinking that they have put a lot of effort when it comes to the development of the app, they have extremely skilled developers and they can carry out the process with ease.
But remember one thing, user perspective is what matters, your developers might be partial, and this might be has a huge weightage considering the competition that you are going to face and the huge amount of money hat’s been invested.
Testing is indeed extra cost, but the amount of risk it mitigates is immense.
But the question prevails! How to test a taxi booking app like Uber?
before we get into that, let’s know about the need in detail.

Why thorough testing is needed
Every customer user app needs thorough testing to succeed in the market. No customer would be willing to use a non-secure or slow app. In this digital age, competition is very high and most likely you will not get a second chance. Here are some reasons why a thorough and meticulously planned testing effort is needed for a taxi booking app:

Security of Customer/Driver Data: the app would include the customer’s and drivers’ personal data (PII). Any security breach in this area can lead to legal complications for the app company and owner.
Integrated Payment and Wallets: Most booking app would have an integrated payment gateway to enable easy payment for the rides. These gateways and payment options need to be tested minutely to make sure the clients’ money is safe.
Easy to Use UI: The app should be designed in such a way that different types of users including aged people and people who are new to the internet can use the app with ease.
Accuracy of data: The app needs to be tested to ensure data accuracy in multiple points. This will include the data of the customer, driver, the trip details, the offers, the fares, the distance calculations, and much more. The accuracy of every data displayed on the app needs to be verified for its correctness.

What to test in a taxi booking app?
Now that we have understood why testing is so important for the taxi booking app, let us look at some important focus areas and test points. While this list is not exhaustive, it will give you a fair idea of how to get started. Feel free to add points as per the app and requirements in hand.
From a Customer Perspective

Customer Data: The customer data in the app needs to be tested to ensure it is accurate. This will include the personal details, the payment details (if they wish to save), the trip details, favorite pick-up and drop location, the offers available, and more.
User and driver registration: Registration for both customers and drivers needs to be tested to check the data is getting saved corrected in the server. The users and the drivers should be able to add, edit, and delete their details as well.
Map Related and live tracking: Testing the map related functionalities are very critical for any taxi booking app. This includes opening the app in the current location, finding cabs in the vicinity, and live tracking of the cab movement before and after confirming the booking.
Time Tracking: The live movement of the cab should be linked to the time taken to reach the destination or time to reach the customer. These values need to be constantly changed to verify the functionality is working fine. This can be tested by simulating a moving vehicle and then calculating the location and time. A critical requirement here would be the refresh. This needs to be decided by the business, ideally, it should be 1 sec or less, so the customer does not see a lag. But based on the system design and the load the business may decide for 2-5 secs also.
OTP: Most apps will have an OTP generation system for authenticating the user at the time of registration and even when boarding a cab. The OTP needs to be validated against the customer data with valid and invalid entries. The number of retries allowed is another important yet overlooked point. If the OTP is regenerated, the system should accept only the latest OTP and none of the previous ones should be accepted. Ignore this if not applicable to your app.
Wallet Transactions and history: Most apps will have an option to load money into the wallet using a pre-established payment gateway. The wallet needs to be checked for money top-up, balance, transaction history, refund, and offers. The same will be true for other payment options like debit card, credit card, UPI, and other options as per the app.
Trip – distance and time: The details regarding the trip needs to be tested. This will include the distance between the pick-up and drop location. The way chosen should be the shortest way with the least traffic based on the congestion points in the location. The estimated time of travel and other details of the trip as per the business needs.
Trip Modification: The user should be allowed to make changes to the trip. This will include cancellation and changing the destination point. In the case of the latter, the trip distance, time, amount, and route should change accordingly. Check if there is a limit on the number of times the user can make the changes. If there is a limit like 2 or 3 then it needs to be tested that the 4th change is rejected by the system.
Cab Sharing: Most of the apps would allow the sharing of the cab between people. In this case, it is important to test the distance between the shared pick-up points. This limit must be set by the business. Check with the requirements and then test to make sure the sharing pick-ups are scheduled within that range.
Driver and cab details: The customers should be able to view all the driver details and his previous customer ratings. They should also be able to see the cab number and the model along with the driver’s contact number. As per the app, these may contain driver pictures as well.
Push messages and SMS: Every app has its own requirements for SMS, email, and push notifications. These will include notifications for booking confirmation, cab arrival, driver details, OTP, trip completion, the amount payable, cancellation request, feedback request, and others. Each of these needs to be tested to make sure they are time-bound as per the business requirements.
Search: One of the most important aspects of the map search. This will include searching for cabs in the current location and location as per the user’s interest. Suggestions for the location once the user starts typing will be good to have feature. The search should show the cabs available in the area along with a route map. It should inform the customer of the distance and time to the nearest cab.
Offers: Every now and then, the company may come with offers and discounts for all or specific customers. The offer code and their validity need to be tested along with any specific requirements for availing the offers. The amount being reduced after availing the offer is another test area.
Feedback and Rating system: The app should include a feedback and rating system for both the customer and the driver. They should be able to give feedback and ratings to each other. These ratings need to be analyzed to improve the drivers and the services provided.
Customer Support and Escalation: The app will have customer support and escalation mechanism in place. This can include support through email, call, or chat. Each must be tested along with the different escalation levels.

From a Driver Perspective

Driver Data: Like the customer data, the app will also contain the driver data, his incentive, the number of trips undertaken, the star ratings (if available), his payment schedule, and other details. This again needs to be tested to make sure the mapping in the database or server is correct and the queries used to fetch the data is as expected.
Trip Visibility and Options: The driver should be able to see the customer search within a specific distance as per his current location as fixed by the business. He should have the option to accept or decline the trip as well. Once accepted the trip should be hidden for the other drivers.
Benefits and Trip history: Most drivers will be paid based on the number of trips they have undertaken, and the benefits would increase with the increase in the daily or weekly completed trip count. All these details along with the payment options and history should be available for the driver to verify.
Hiding Customer Personal Data: Customer data is very critical especially the phone numbers. This information need not be shared with the drivers. To contact the customers there should be a hotline number and the customer details should be hidden from the driver.

Types of Testing
For all the above test cases, there are different types of testing that will be done. Here is a list of these:

Manual Testing: Critical business functionalities need to be tested manually. Manual testing is also needed in cases where the team does not have the time or money for automation or when the automation feasibility for the features is low.
Automation Testing: The app will have a lot of validations. If the testing is to be done only once, then automation is not required. But if there are likely to be regular updates or new features added, it would be better to have an automation suite in place to reduce the future testing efforts and save time as well.
Security Testing: The app server or database contains personal data of the customers and the drivers. This will include the names, address, phone number, mobile number along with the payment details that can include the bank or card numbers. The security of this data is very important. The app should be safeguarded against external attacks.
Performance Testing: Based on the anticipated load performance testing needs to be done so that the search, map loading time, and other transactions are well within the SLA at peak and off-peak loads. Based on these results the business will decide to scale-up the infrastructure if needed.
Integration Testing: There are several systems involved in the app. This includes the GPS tracking or mobiles of the driver and customer, the database or server, and the booking app. The integration between these systems needs to be verified for accuracy and data flow.
DB testing: Customer and driver details along with all the trip information are store in the database. Hence, DB testing is imperative. While testing we need to ensure that the basic operations like adding a record, editing a record, deleting a record, fetching the record are being performed as per the expectation.
Exploratory Testing: Exploratory testing is a kind of informal testing in which the user would just explore the application trying to go through all the different pages and verify that nothing is broken.
Responsive Testing: Responsive testing needs to be done to ensure that your taxi booking app renders itself well in devices with different screen sizes and resolution. With so many new devices entering the market and the extensive usage of the internet, responsive testing of the app needs to be taken very seriously.
UAT Testing: The ultimate testing for any app or software must be the UAT or User Acceptance Testing. UAT gives the usage pattern and the most frequently used areas of the app. This will be helpful in deciding the future features of the app.

How do I test the Uber app?
Apps like uber are bound to be installed across many devices with varied OS versions. Performance testing has to be done at intervals to make sure that the app is working fine and it has what it takes to meet up customer expectations.
While testing make sure that

Complete assessment of the business requirement of the apps
Identify the important performance testing metrics
Create perfect and realistic test scenarios
Analyze and validate the test result and measurements
Preparation of reports that can also be useful for developers.

Tips for testing apps like uber

Apart from the normal workflow of the registration module, you must also make sure that social media login and integration is carried over the system with ease.
Check email authentication process to make sure that your domain will not be marked as spam
Make sure that there are unnecessary links attached to the mail send by the system
Make sure that the user is able to differentiate auto-generated messages
Make sure that the geographic information system (GIS) is in sync with the system and functionalities
Check the OS compatibility of the app with various versions
Make sure that the information provided to the user is concise and precise
Proper localization testing needs to done to make sure that it’s not hurting any sentiments
Real drivers and passengers have to be used for testing rather than a simulated environment
A payment gateway is integral for taxi booking apps. make sure that it doesn’t have any loophole and is working fine
Trace out all the security loopholes in the system
Test the authorization workflow and functionality
Gamification is indeed the star nowadays. Make sure that it’s in a way that will make the driver and the customer feel rewarded
Test the system in varied internet strength and load

Top 10 Taxi booking Apps

Uber
Lyft
Ola Cabs
Taxify
DIDI
Cabify
Lecab
Curb
Gett
GoCatch

Which are the tools that can be used for taxi booking app testing?
While the listed set of testing might be overwhelming, here is a list of tools available in the market to get you started.

Appium and Appium Studio
TestComplete
Calabash
Webload
Zed Attack Proxy
Android Debug Bridge
Lambda Test
Studio Press
DBFit, SQLUnit
Visual Studio Team Edition

Hope you have a fair idea now about how to test a taxi booking app now. This should be enough to get you started and rest you can improvise when you are at it.

AngularJS Testing Tutorial – Cypress, Karma and Protractor

Posted on May 7, 2020 by tbsupadminnxtbackendacc

AngularJS testing using selenium is not a good approach. Due to the asynchronous behavior of the application selenium is not able to handle the asynchronous calls.
So it is necessary to make use of angularJS testing tools so that asynchronous behavior of the application can be handled. Let us see some good approaches to test angular JS websites below.
Unit Testing AngularJS Apps
To make sure that unit testing is happening easily when it comes to AngularJS Testing, Angular JS has been provided with dependency injection for your XHR requests. The main reason behind is to simulate requests. The model can also be tested by altering the DOM directly. in short, individual sort function can be tested in isolation.

What is Karma?
Karma is a JS runner created by the angular JS team themselves. and is one of the best when it comes to AngularJS Testing.
Jasmine is the framework for testing angular JS code while karma provides us with various methods which makes it easier to call Jasmine tests.
For installing karma, you need to install node JS in your machine. After installing node JS, install Karna using npm installer.
How to test AngularJS apps using Karma?
First of all,
One can install karma using below command
npm install karma –save-dev
After running this command, karma dependencies will be installed. It will be present in package.Json after you run the above command. For making karma available globally use -g option so that you can invoke it from anywhere.
Now, the next step is to install karma plugin which would help us in using the jasmine framework and google chrome browser. Run the below command:
npm install karma-jasmine karma-chrome-launcher –save-dev
After running this command, start making tests in command prompt. For creating tests, run the following command.
mkdir tests        // for making tests directory
touch tests/test1.controller.test.JS     //For creating a test called test1
After creating a test, now it is time to put code in test1.
describe(test1,function(){
beforeEach(module(test1));
var$controller;
beforeEach(inject(function(_$controller_){
$controller=_$controller_;
}));
describe(‘sub’,function(){
it(‘1 – 1 should equal 0’,function(){
var$scope={};
varcontroller=$controller(test1Controller,{$scope:$scope});
$scope.x=1;
$scope.y= 1;
$scope.sub();
expect($scope.z).toBe(0);
});
});
});
Now, after creating the test you should know how to create a test runner, and before creating that we should know the configuration required for the test runner. For configuring the test runner perform the following steps.
karma init karma.conf.JS
Now, for running the tests using the test runner run the following command.
karma start karma.conf.JS
The test output should look like the underlying code.
> @ test /Users/devuser/repos/test1
> ./node_modules/karma/bin/karma start karma.conf.JS
INFO [karma]: Karma server started at http://localhost:8080/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 80]: Connected on socket 2absOkNfa1asasaX0fCJ with id 66276373
Chrome 80 test1 encountered a declaration exception FAILED
ReferenceError: module is not defined
at Suite.<anonymous>(/Users/devuser/repos/repo1/tests/test1.controller.test.JS:3:13)
at /Users/devuser/repos/repo1/tests/test1.controller.test.JS:1:1
Chrome 80): Executed 1 of 1 (1 FAILED) ERROR (0.01 secs / 0.005 secs)
Now, add the following lines to your package.JSon.
{
“scripts”:{
“test”:”karma start karma.conf.JS”
},
Now with the help of this script, we will be able to run any test using npm command. Using the below command, run the jasmine tests.
npmtest
Now, it is time to add the controller logic and for adding it run the following commands.
mkdir app
touch app/test1.controller.JS
Add the following code in test1.controller.JS
angular.module(test1,[]).controller(‘testController’,functiontestController($scope){
$scope.sub=function(){
$scope.z=$scope.x-$scope.y;
};
});f
For adding the angular dependencies, run the following commands. Make a directory called lib in your project and then add all libraries in that folder.
mkdir lib
curl -o lib/angular.min.JShttps://code.angularJS.org/1.4.0-rc.2/angular.min.JS
curl -o lib/angular-mocks.JShttps://code.angularJS.org/1.4.0-rc.2/angular-mocks.JS
Now, it is time to edit the karma config file so that it comes to know about the test folder and the library folder so that jasmine tests can run successfully.
files:[
‘lib/angular.min.JS’,
‘lib/angular-mocks.JS’,
‘app/*.JS’,
‘tests/*.JS’
],
Now, run the tests using the npm test. Your test will run now successfully.
How to test AngularJS applications using Protractor?

Protractor is impeccable when it comes to AngularJS Testing. In Angular JS applications are hard to test since the application web elements cannot be captured very easily.
Angular JS applications have some extra attributes like ng-repeater, ng-controller, and ng-model which can be identified using Selenium locators. Protractor is a NodeJS program which is written in JavaScript. The pre-requisite of using Protractor is Selenium and NPM.
Let us see how you can proceed with the installation of Protractor. Run the following command to start with the installation of the protractor.
npm install –g protractor
It will install protractor in your system. Using -g will make it available globally in your system. Now, after installation of protractor If you want to check the version of the protractor. You can find the following by running the following command.

Protractor –version
For running the protractor tests against the application under test, you would need webDriver manager. Now, you must update the webDriver manager to the latest version. For updating it, run the following command.
webdriver-manager update
Now you must be imagining how would you start the webdriver-manager. You can start it by running in the background by running the following command. It will then listen to all your protractor tests which have to be run against the angular JS application.
webdriver-manager start
Now to see if the webdriver manager plugin if it is properly running or not. Go to the URL: http://localhost:4444/wd/hub/static/resource/hub.htmland you will see the webdriver manager plugin running on it.
Now, we will see how to design the test cases in protractor. To start with designing o the test cases you need 2 files. One is the spec file and the other is the config file. The configuration file has the location for the protractor tests. Also remember, chrome is the default browser for a protractor. While the second file, the spec file has the logics and locators which would be used to interact with the application.
Now, let’s take a test case in which we have to go to URL: https://angularJS.org, and then you have to type your name in the textbox. After entering you will see your name as Hello Name!
Now, let us start with the steps which are required for making this test case and to execute it. In your folder, you will have 2 files. One is spec.JS and the other is conf.JS. The logic for spec.JS which will be there in it.
describe(‘Enter yourname, function() {it(‘should add a Name as your name, function() {browser.get(‘https://angularJS.org’); element(by.model(‘yourName’)).sendKeys(‘Name’); var name= element(by.xpath(‘html/body/div[2]/div[1]/div[2]/div[2]/div/h1’));expect(name.getText()).toEqual(‘Hello Name!’); });});
Now, if you see that describe comes from the Jasmine framework. It is basically a module and it can be a class or a function. We are giving this module name as “Enter Your Name”. So, for starting the function we start it with describe keyword. Just like a class can have many methods or a TestNG class can have so many test cases. Similarly, in the Jasmine framework, it starts a new test case.
browser.get(‘https://angularJS.org’);
This command is used for opening the browser with URL mentioned as https://angularJS.org. Now, you must identify the elements. So, you have to inspect the element just like you do in Selenium. You can use By.model for the elements who have ng-model as an attribute.
You can store Web elements in a variable. You can declare a variable using var keyword. Now, it is time to have some assertions. You get the text out of this web element and then compare it to the expected text.
Now, you are done with spec.JS and let us start with the conf.JS. You have to define the path of spec here so that tests can be identified easily.
Paste the following code in conf.JS
exports.config = {seleniumAddress: ‘http://localhost:4444/wd/hub’, specs: [‘spec.JS’]};
Selenium address is the location where it can communicate with the selenium webdriver. Spcs tell the location of spec.JS
Now, for running the test, first navigate to the directory in which spec.JS and conf.JS are located. First thing to keep in mind that webdriver-manager should be started. If not started, you have to first start it with following command.
webdriver-manager start
Now, it’s time to run the configuration file. After starting the webdriver-manager plugin, run the config.JS file using protractor. Fire the following command.
protractor conf.JS
You have seen how many specs got passed and how many got failed.
Now let’s see how the failure is going to be reflected in the console. We make the assertion false.
Modify the code in spec.JS
describe(‘Enter your name, function() {it(‘should add a Name as your name, function() {browser.get(‘https://angularJS.org’); element(by.model(‘yourName’)).sendKeys(‘Name’); var name= element(by.xpath(‘html/body/div[2]/div[1]/div[2]/div[2]/div/h1’));expect(name.getText()).toEqual(‘Hello!’); });});
You will see F which means failed test case. You will get to know the complete description where the test case got failed.
Now, you must be imagining how would the reports be integrated with Jasmine. Let’s install the Jasmine reporter. Run the following command:
npm install –save-dev jasmine-reporters@^2.0.0
If you want jasmine reporter to installed globally. For installing globally, run the following command.
npm install –g jasmine-reporters@^2.0.0
You have to now modify the conf.JS. You have to add Jasmine reporter in it. Add the following code in it.
exports.config = {seleniumAddress: ‘http://localhost:4444/wd/hub’,      capabilities: {          ‘browserName’: ‘Chrome’      },      specs: [‘spec.JS’],     framework: ‘jasmine2’ ,onPrepare: function() {          var jasmineReporters = require(‘C:/Users/User1/node_modules/jasmine-reporters’);jasmine.getEnv().addReporter(new jasmineReporters.JUnitXmlReporter(null, true, true)          );     }   };
Now, run the tests using protractor conf.JS. You will see the junitresult.xml in the folder path given in conf.JS.
Open the XML file and see the result of the test case. In this way, you can take the help of protractor to test angular JS websites.
How to test the AngularJS app using Cypress?
Cypress is very close to the application. It just has a very thin layer between production code and testing code. It is Javascript E2E testing framework.
It is an open-source AngularJS Testing framework Cypress has bundled various packages such as Mocha, Chai, and Sinon. The only supportive language with Cypress is Javascript. When you open the cypress application using command cypress open, the following application will open.
This application is divided into two parts. On the left side, you write commands. There are different keywords to it. VISIT is for opening the URL and GET is for getting a webelement. CLICK is for clicking on the webelement. Using ASSERT, we can add assertions to our test cases.
For installing Cypress, you should have node.JS installed in your machine. You can then use the npm installer to add dependencies of Cypress.
npmicypress -D
Now for opening the cypress test runner, run the following command.
npx cypress open
If you want your application and Cypress to run at the same time then you have to make some changes in your package.JSon.
“cypress”: “concurrently \”ng serve\” \”cypress open\””
Add these lines in package.JSon.
Now, run the following command
npm run cypress
When you add a new project in cypress then you will have below folder structure.
Fixtures have static data that has to be used by your tests. You can use them by cy.fixture() command. In the integration folder, you will have your integration tests. The plugin helps you to tweak to your test cases. Just like plugins have a file named index.JS which have a method which will run before every spec file. In Support files, you can have your reusable code.
Now, it is time to create your first test in the integration folder. You name it as test1.spec.JS. You will see it in the Cypress test runner also. Cypress API is present under the global cy project. Now let us put some code in it.
describe(“Test1”, () => {
it(“should visit home page”, () => {
cy.visit(“http://localhost:4200/login”);
});
});
It makes use of description and it blocks from the mocha syntax. It makes the beginning of the test cases. Once you will run this test In the test explorer, on the right side, the execution starts.
When you will run Cypress for the first time, you will see that the cypress.JSon file will get generated. In this, you can store your configuration values. Now let’s store our base URL in cypress. JSON so that we don’t have to change the URL in every test case.
{
“baseUrl”:”http://localhost:4200″
}
It’s time to change the code in spec.JS also.
describe(“Test1”,()=>{
it(“shouldvisit home page”,()=>{
cy.visit(“/login”);
});
});
Now for getting webelement, you can make use of a cypress selector background in the test runner. It is present on the left side of the test runner. You can get the XPath from there.
Use this way to get the webelements.
cy.get(‘.btn-link’).click();
cy.url().should(‘include’, ‘/register’)
This assertion will check the check has registered keywords in it. Hence, we are done with the first test case in cypress.

Conclusion
Now, we have seen different ways of AngularJS Testing. Make use o
f these and test the application in the best possible ways. Optimize your code and have the best test integration practices so that the client can be satisfied with your test metrics. All the best.

24 Top software testing companies in USA 2022 Update

Posted on April 21, 2020 by tbsupadminnxtbackendacc

Which are the prominent software testing companies in the USA?

Before any company puts up software they certainly check that is it working and will be brought to use as per the requirements of the company.

if you think that finding the best one from the USA is like the same story of the needle in a haystack, you have reached the right place. Here is the list of best software companies which are there in the USA which are known for providing QA/testing services.

Top software testing companies in USA (Quick Access Table)

Company Name	Founding year	Location	Employee Strength	Core Services
TestBytes	2013	New York NY	51 – 200	Mobile App Testing, Game Testing, Test Management Services, Automation Testing, Security Testing, Web Application Testing, Software Performance Testing, Load Testing, Functionality Testing, Browser Compatibility Testing, and Localization Testing
Alqa	2004	Colorado, The United States	700	Manual and Automation Testing in domains: Finance, Health, Banking, and eCommerce.
Quality Logic	1986	West Emerald Street, Boise, ID 83704 USA	100-250	Web and mobile development, OTT and streaming media, Automation and Security testing
ScienceSoft	1990	Dallas, United States	75	Manual Testing, Automation Testing, and DevOps.
DeviQA	2010	NYC, United States	50 – 250	Web/ Mobile, API, E2E, UAT, UI automation using top notch tools, performance testing, stress testing, load testing, and QA consultancy
Hidden Brains InfoTech	2003	Schaumburg, IL, United States	50 – 250	Development, IOT, Blockchain technology, Big Data, AI, Product Maintenance and Support
Powercode	2002	Random Lake, Wisconsin	11-50	Web and App Development, Testing and maintenance
BairesDev	2009	San Francisco, California	1001-5000	Web and App Development, Testing and maintenance
Testmatick	2009	New York, USA	51 – 200	Mobile App Testing, Game Testing, Test Management Services, Automation Testing, Security Testing, Web Application Testing, Software Performance Testing, Load testing, Functionality Testing, Browser Compatibility Testing, and Localization Testing
QASource	2002	CA, USA	500-1000	AI, Automation Testing, Mobile Testing, API Testing, QA Outsourcing Services
Zymr Inc.	2012	California, USA	50-249	Web and App Development, Testing and maintenance in the field of Cloud and Cybersecurity
QATestLab	2005	Kyiv, Ukraine	50-249	Mobile Testing, Functional Testing, Automated Testing, and Performance Testing
LambdaTest	2017	San Francisco, USA	11-50	Cloud Mobile, Web and API Testing
Algoworks	2006	California, USA	200-500	Salesforce development and Testing
Nexsoftsys	2008	NYC, USA	11-50	Software Development, AWS, Big Data, Block Chain, Data Integration, ETL, Software IT Outsourcing, QA and Testing Services
Awsquality	2016	Ruston LA, USA	11-50	Salesforce development to testing
Synergytop	2014	California, USA	50-249	Design and Development of Web and mobile applications along with Quality analysis
Abstracta	2008	California, USA	50-249	Extensive testing in the domain: BFSI, Retail, Healthcare, and Technology
Rademade	2011	Buenos Aires, Argentina	50-250	Design of product from development to maintenance in the domain: FinTech, BFSI, Healthcare, and Blockchain domains
Codebright	2015	Virginia, USA	50-250	Strategic Consulting, User experience, Project Management, Web Development, Mobile Development, Quality Assurance, and AI
Agile-infoways-PVT-ltd	2006	Dallas, USA	700-1000	Mobile App Development, Website Development, Web/Mobile App Design, eCommerce Solution and Quality Assurance
Systematix-infotech-pvt-ltd	2015	NC, USA	50-249	AI, ML, RPA, Development, CRM, and Quality Assurance
Sunflower-lab	2010	Ohio, USA	50-100	Mobile Testing, Functional Testing, Automated Testing, and Performance Testing in domain: Finance, Real Estate and Oil and Gas
Blue-label-labs	2008	NYC, USA	50-250	Strategy Development, Design, Development and Quality Assurance of Product

TestBytes

Location: 65 Broadway Suite 1101, New York NY 10006
No of Employees: 50 – 200
Founded In: 2013

Testbytes provide all kind of testing services in the testing domain but what makes them apart are Mobile App Testing, Game Testing, Test Management Services, Automation Testing, Security Testing, Web Application Testing, Software Performance Testing, Load Testing, Functionality Testing, Browser Compatibility Testing, and Localization Testing.
One of the best communities of software testers with a top-notch testing skill set. you can reach out to them at info@testbytes.net.
Testbytes also have a strong Linkedin presence with more than 25k followers

2. A1qa

Location: Colorado, The United States
No of Employees: 700
Founded In: 2004

A1qa is a software testing company that has its headquarters in Lakewood, Colorado. It has a strength of around 700 QA professionals, and it is been 16 years since a1qa has been providing software testing services.
Their testing services include consulting, full-cycle testing, test automation, web app and, mobile app testing, pre-certification testing, and documentation services.
Talking about the cost of services they provide; it entirely depends on services but on average, they charge you between 25$ – 49$ per hour.
They are located at S. Wadsworth Blvd., Suite 485, Lakewood, Colorado 80235
The United States and you can contact them at +17202075122.

3. Quality Logic

Location: West Emerald Street, Boise, ID 83704 USA
No of Employees: 51-200
Founded In: 1986

Quality Logic is a QA company based on locations such as West Emerald Street Boise, 1st Street, Suite 103 Simi Valley, CA 93065, NW 64th Street, Suite 120 Oklahoma City, OK 73116 USA
As their website says their testing services range from mobile apps to 3D printers
They also possess a variety of testing tools that are customized for various specifications

4. ScienceSoft

Location: Dallas area, TX, United States
No of Employees: 75
Founded In: 1990

They are a renowned software testing company
It is been 30 years since they have created their name in the USA for their testing services. In this span, they have completed around 500 projects.
Their domain expertise lies in Retail, BFSI, HealthCare, telecommunications, and Entertainment. They help other companies to have correct testing practices and help them build a bug-free product.
They have a team of 75 software testing professionals who have a forte in testing according to compliance: ISO 9001:2015.

5. DeviQA

Location: NYC, United States
No of Employees: 50 – 250
Founded In: 2010

DeviQA has been offering testing services in the last 10 years in the USA. Always top number in the automation testing awards.
They deal with a lot number of testing services such as Web/ Mobile, API, E2E, UAT, UI automation using top-notch tools, performance testing, stress testing, load testing, and QA consultancy.
They have tested their hands in varied domains and some of their top domains are cybersecurity, education, travel, and BFSI.
They believe in providing the top-level services, but customer’s data is secure which is their top priority.

6. Hidden Brains InfoTech

Location: Schaumburg, IL, United States
No of Employees: 50 – 250
Founded In: 2003

Hidden Brains provides testing services to a lot of clients in the USA.
Talking about their number of clients, they have around 2000 clients which are spread around 103 countries. They have been catering to the services in 100+ domains.
Their professionals are top-notch software professionals who are well acquainted with the best software testing practice and methodologies.
The company is Microsoft Certified Partner and has won various awards in the software testing industry.

7. BetterQA

Location: Random Lake, Wisconsin
No of Employees: 11-50
Founded In: 2002

They have their headquarters at Ukraine
Even if it is test automation practices or development, they believe in providing the best at a very rational cost.
It is been 15 years since they are providing services to customers and customers are happy with the services.

8. BairesDev

Location: San Francisco, California
No of Employees: 1001-5000
Founded In: 2009

It is one of the most dynamic and fast-growing IT companies in Latin America.
They help in making a product from development to maintenance. Some of their well-known clients are Pinterest, Rolls-Royce, Motorola, and others.
Their forte and expertise lie in Testing, renowned to follow all the well-known agile practices.

9. Testmatick

Location: New York, USA
No of Employees: 51 – 200
Founded In: 2009

The company was founded in the year 2009 and has been headquartered in New York. It is one of the top testing service providers in New York.
They have a strong team of testers who can start working on your project as soon as possible and can help you show the graphs where your product is lacking.
Testmatick has a strength of around 200 members.

10. QASource

Location: CA, USA
No of Employees: 500-1000
Founded In: 2002

QASource have around 17years of experience
They charge you around 25$ – 49$ per hour with strength between 500 -1000.
Their top clients are eBay, IBM, ORACLE, Facebook, prudential and others. You can visit their website qasource.com for more information.

11. Zymr Inc.

Location: California, USA
No of Employees: 50-249
Founded In: 2012

Zymr is a full-stack service provider company providing various services ranging from development to maintenance.
Around 1500 sprints have been successfully delivered by them.
The company is known to provide services of software testing plus web and App Development, testing and upholding in the ground of Cloud and Cyber security and so on

12. QATestLab

Location: Kyiv, Ukraine
No of Employees: 50-249
Founded In: 2005

QATestLab is a software testing service provider in the USA which has been providing its services since 2005.
They have a team strength of 50-249 members. They serve various industries such as e-commerce, tourism, and other government projects.
The company provides all kinds of testing services in the testing domain such as Mobile Testing, Functional Testing, Automated Testing, and Performance Testing.
Loomia, BlazeMeter, imi, Freestyle Solutions, and PaperTrail are some of the top clients of QATestLab.

13. LambdaTest

Location: San Francisco, USA
No of Employees: 11-50
Founded In: 2017

LambdaTest is a software testing company that has its headquarters in California, USA. It has a strength of around 250 QA professionals, and it is been 3 years since LambdaTest has been offering software testing services.
They have around 2000 combinations of physical devices and browsers ready for testing.
They offer you their selenium grid with which you can easily automate your automated tests in a parallel way.

14. Algoworks

Location: California, USA
No of Employees: 200-500
Founded In: 2006

One of the top esteemed testing service providers in the USA. It is been operating its functions in The USA for 14 years. Algoworks provide various services such as salesforce development to testing.
They specialize in salesforce testing. They have a strength of 1000 consultants which provides the best testing services to build the right product.
They have been catering to 500 fortune companies such as Dell and Amazon for many years and in this span of a career.
Architects of Algoworks will formulate the best strategy for you to test your software in a very rational cost.

15. Nexsoftsys

Location: NYC, USA
No of Employees: 50-249
Founded In: 2008

Nexsoftsys is a technological partner which provide its testing services to various companies in the USA.
They have expertise in various technologies such as Java, Golang, Python, Magenta, and Android.
It is been 11 years since they have created their name in the USA for their testing services. In this span, they have completed around 500 projects.
They have a team of 250 software testing professionals who have a forte in testing according to the best software testing practices.

16. Awsquality

Location: Ruston LA, USA
No of Employees: 11-50
Founded In: 2016

Awsquality has been offering testing services in the last 6 years in the USA. Prominent in salesforce development and testing.
They deal with a lot number of salesforce services such as Salesforce.com, Force.com, ERP, and others.
They have tested their hands in varied domains and have delivered more than 150 projects so far.
Awsquality believes in providing top-level services, and this is the reason they have been serving Fortune 100 companies so far.

17. Synergytop

Location: California, USA
No of Employees: 50-249
Founded In: 2014

Synergytop provides testing services to a lot of clients in the USA. They provide extensive services such as the Design and Development of Web and mobile applications along with Quality analysis.
Talking about their strength, they have around 250 professionals onboarded who provide the best services in the industry.
They have been catering to the services since 2014. Their professionals are top-notch software professionals who are well acquainted with the best software testing practices and methodologies.
They offer services in a very rational cost. They are located at 11832 Cypress Canyon Road, Suite 2, San Diego, California 92131 United States.

18. Abstracta

Location: California, USA
No of Employees: 50-249
Founded In: 2008

Headquartered in California, USA. Abstracta is a renowned name
They have been serving various domains such as BFSI, Retail, Healthcare, and Technology.
It is been 12 years since they are providing services to customers and customers are happy with the services.
Their main product is named GXTest which is extensively used for mobile testing..

19. Rademade

Location: Buenos Aires, Argentina
No of Employees: 50-250
Founded In: 2011

It is one of the most dynamic and fast-growing IT companies in Ukraine. They have a team count of around 250 members.
They help in making a product from development to maintenance. Some of their well-known clients into FinTech, BFSI, Healthcare and Blockchain domains. Their forte and expertise lie in Testing.
They follow all the well-known agile practices. They are going to charge you between 25 – 49$ per hour depending upon the project.

20. Codebright

Location: Virginia, USA
No of Employees: 50-250
Founded In: 2015

The company was founded in the year 2015 and has been headquartered in Virginia.
They have a strong team of testers who can start working on your project as soon as possible and can help you show the graphs where your product is lacking.
Software testing one of their service offering among others

21. Agile-infoways-PVT-ltd

Location: Dallas, USA
No of Employees: 700-1000
Founded In: 2006

One of the top testing service providers in the USA for the last 13 years.
They have delivered more than 2200 projects so far and have a very huge client base of 750 numbers.
Their services include, mobile app development, digital marketing, e-commerce development

22. Systematix-infotech-PVT-ltd

Location: NC, USA
No of Employees: 50-249
Founded In: 2015

Systematix is a CMMI Level 3 company which is ISO 9001: 2015 certified. It provides various services from AI, ML, RPA, Development, CRM, and Quality Assurance.
They have been certified with various certifications such as Google Certified Partner, DataStax Partners, and Microsoft Gold Partner.
They deal with various technologies such as JavaScript, Tableau, and Python. They have delivered around 2500 projects in much less duration.

23. Sunflower-lab

Location: Ohio, USA
No of Employees: 50-100
Founded In: 2010

It is a software testing service provider in the USA which has been providing its services since 2010.
They provide all kinds of testing services in the testing domain such as Mobile Testing, Functional Testing, Automated Testing, and Performance Testing.
Sunflower Labs services include Custom Software Development, Web App Development, Mobile App Development, IoT App Development, Wearable App Development, Alexa Echo App Development, AR/VR App Development, and Strategic IT Consulting

24Blue-label-labs

Location: NYC, USA
No of Employees: 50-250
Founded In: 2008

Blue-label-labs is a software testing company that has its headquarters in New York, USA. It has a strength of around 250 QA professionals, and it is been 11 years since it has been offering software testing services.
Till now they have developed 250 applications so far. They provide services from development to post-launch maintenance.

Conclusion
We do know that there are many software testing companies in the USA. However, the names that we have mentioned in this blog are considered as some of the best and provide quality services in QA.

Difference between regression testing and retesting

Posted on April 15, 2020 by tbsupadminnxtbackendacc

Regression testing	Re testing
Done whenever there is a change in code	A confirmation technique used once the defect is fixed
To assure that new changes hasn’t caused new issues	To find out whether the issue has been rectified and functionality is restored
Can be done parallel with retesting	Should be performed before regression testing
Passed test cases are used	Failed test cases are put to use
Defect verification is not apart	Defect verification is a part
Can be used to check unexpected results	Confirms that the original fault has been corrected
Automation is the key	Can’t be automated

Difference Between White box and Black box Testing

Posted on April 15, 2020 by tbsupadminnxtbackendacc

Black Box testing: it’s kind of testing where the tester doesn’t know the architecture of the software he is testing. These tests can either be functional or non-functional. It’s high-level testing that’s meant to test the behavior of the software.
White box testing: White box testing is used to test the internal structure of the system. In this type of testing, usually code statements, branches conditions, etc. are covered. White box testing is considered a low-level testing often called a glass box, transparent box or code base testing.

Difference between use case and test case

Posted on April 13, 2020 by tbsupadminnxtbackendacc

Use case	Test case
Set of variables, conditions or steps used to define the interaction between a role and a system to attain certain objectives.	Conditions or variables used to define the functionality and behavior of a software
Prepared by business analyst	Prepared by test engineers
Different case can be combined	One at a time
Use case is something that has to be designed	Testcase is something that has to be executed
Describes the flow of events of the software	A document that contains events, action and expected result of the software
Provided to developers	Provided to testers
Managed by diagrams	Managed by function tests
Requires proper document and research	Requires test scripts are required

Smoke Testing Vs Sanity Testing: What’s the difference?

Posted on April 13, 2020 by tbsupadminnxtbackendacc

Smoke testing vs sanity testing! which one hail? To be frank, each process is important and the situation and requirement demand which one to choose from.

However, the comparison depicted here in this blog will help you understand more about smoke and sanity testing.

Smoke Testing

Smoke Technique is one of the testing types that’s instigated from hardware testing.

This technique comes into the scenario at the time of attaining build software from the development team.

The main reason to go for the smoke testing is to find out whether the software which is built is testable or not.

It is usually done at the point where the software is built. This process has been given another name as well. It is actually called “Day 0″.

The smoke Testing process is counted as the best one because it is a time-saving one.

The most astounding feature about the process is that the time consumed is less since the testing is only done when the main functions of the application are not properly working or if certain major bugs are not sorted till that moment.

The main emphasis of Smoke Testing is on the working of the major features and primary functions of the application.

Going for the test is the basic and important feature of an application before one goes for the deep, accurate testing (before understanding all probable positive and negative values) is referred to as smoke testing.

The whole emphasis while going for the smoke testing is on the productive flow of the claim and it possesses only the verified data, not the unacceptable one.

In smoke testing, the process confirms every build is testable or not; hence it is called Build Verification Testing.

When smoke testing is being conducted then one can look for the blocker bug at the initial period only so that the test engineer just doesn’t have to sit idle, or they can go on further and do the analysis of the independent testable modules.

Which test comes first smoke or sanity?

Smoke testing is usually performed on a new build/feature. The main motto behind smoke testing is to ensure that the software is ready to be tested.

Sanity testing is performed when time is not at the disposal of the dev team. Smoke testing is done first and then the application goes through quick regression or sanity testing

What is the process for conducting smoke testing

The process to Conduct Smoke Testing:

For Smoke testing, there is no requirement to create test cases. In this, the only requirement is to pick the required test cases from the already created test cases.

As stated before too, Smoke Testing emphasis the workflow of core applications so that choosing test case suits that cover the main functionality of the application is done.

It is vital to bring down the number of test cases as much as possible and the time of implementation should not be more than half an hour.

When smoke testing is performed

Usually when the new build is implemented then one round of smoke testing is conducted because there are chances of blocker bugs in the latest one which is created.

However, there can be a certain change that might have wrecked a major feature that as fixing the bug or adding a new function which can affect a major piece of the original software, or the smoke testing is done where the installation is taking place.

When the stable build is all installed then smoke testing is conducted to find the blocker bug.

Why is smoke testing done?

There are certain reasons because of which smoke testing is conducted. Stated below are the important ones.

The smoke testing is basically done to make sure that the product is testable.
The smoke testing is done in the beginning so that the bugs which are there in the basic features could be detected and further can be sent to the development team so that the development team gets a lot of time to get rid of the bug.
Smoke testing is done to ensure that the application is installed in the approved manner.

Types of Smoke Testing

The Smoke testing is further divided into two types:

Formal smoke testing

In this, kind of testing the application is sent to the Test Lead by the development team.

Further, the test lead will divide the task of testing the app among respective tests along with reports which state the whole scenario after going through the smoke testing.

Once the testing team is over with smoke testing, they will report for the testing done to the test lead.

Informal smoke testing

Here, the Test lead notifies that the application is all set for further testing.

The test leads do not give any specific instructions to perform the smoke testing, but still, the testing team begins with the testing procedure of the application by going for the smoke testing.

Example for smoke testing

A detailed explanation about smoke testing and example for the process is given in this blog, please go through

Sanity Testing

Sanity Testing is a division of regression testing. Sanity testing is usually done to make sure that the code changes which are being done are carried out properly.

Sanity testing is a general strike to note down that the testing for the build can further go on or not.

The main emphasis of the team while doing the sanity testing process is to confirm the functioning of the application and not about the detailed testing.

Sanity testing is usually carried out on build where the production deployment is essential right away similar to a critical bug fix.

The functionality of Sanity Testing:

The main reason for which sanity testing is conducted is to know about the changes or the projected functionality is being done in the same order as it was mentioned.

If the sanity test fails, the software product is declined by the testing team to stay on a safer side in terms of time and money.

It is carried out once the software product has carried out the smoke test and the Quality Assurance team has acknowledged for the further testing.

Features of Sanity Testing:

Division of Regression Testing:

Sanity testing is further a division of regression testing and emphasizes the smaller part of the application.

No script required

There is no such script available for sanity testing most of the time.

No documentation

There is no documentation required for the sanity testing so it is undocumented.

Narrow and extensive

Sanity testing is narrow but at the same time it is an extensive approach of testing where limited functionalities are covered in depth.

Carried out by testers

Usually, sanity testing is carried out by the testers only.

Advantages of Sanity Testing:

Sanity testing is a great aid when it is about quick identification of the defects in the main area of functionality.
It can be further performed in a lesser time as there is no need for any kind of documentation for performing the sanity testing.
During the sanity testing if there are defects found then the project is further declined and this is a great way to save out on time which can be further utilized to carry out regression tests.

Example for Sanity Testing

For instance, build 2 has a multitude of feature which are tested and fixed accordingly.
Now build 3 with added features and integration has again come for testing
To make sure that the new features haven’t affected the existing ones, smoke testing will be performed
Once that’s done a high-level analysis of the entire software will be carried out to ensure no new bugs have surfaced.

Sanity Testing Process

The main reason for which the sanity test is performed is to know about the incorrect outcomes or faults which are not accessible in the constituent process.

Even it is done to make sure that the newly added features do not disturb the functionalities of ongoing features.

Further, three steps are implemented in the sanity testing process that is Identification, Evaluation, and Testing

First step- Identification

In the sanity testing process, the first step is the Identification one where one finds out the newly added constituents and features along with the adjustment there in the code while going for the process of fixing the bug.

Second step- Evaluation

Once the identification step is completed, one needs to analyze the recently implemented constituents, characteristics and further change them so as to verify their proposed and suitable working as mentioned in the stated requirements.

Third step- Testing

After performing the identification and evaluation step one needs to go further to the third step which is testing.

In this step, we examine and evaluate all the connected constraints, constituents, and fundamentals of all the above analyzed attributed and change them so as to ensure that all of it is working properly.

Once all the above-stated steps are going in the right manner, the build can be made to undergo more exhaustive and strenuous testing, and the release can be carried further for the thorough testing process.

Comparison of Smoke Testing and Sanity Testing

Thus both the tests have their own unique traits which make them required for the software processes.

Smoke Testing	Sanity Testing
Used for checking critical functionalities of a software	The focus will be on a particular area or minor functionalities
Performed to check the stability	Used to verify the rationality
Both manual and automated test cases can be used	Generally, sanity testing does not have a test script or test cases
Usually performed before passing the build to the testing team	Executed before UAT and regression
Carried over by developers	Performed by testers
A subset of acceptance testing	A subset of regression testing

Conclusion

Hope you got to know the difference between sanity testing and smoke testing and are able to understand, smoke testing vs sanity testing has no meaning to it as both processes have equal importance.

Load Testing vs Stress Testing: What’s the difference?

Posted on April 13, 2020 by tbsupadminnxtbackendacc

Load Testing vs Stress Testing what’s the striking differences between both the process?
In the following sections, we will discuss in detail load and stress testing. People often get confused between these 2 and refer to them as a load and stress test. But there are fundamental differences between these 2 performance tests, as we will discuss in the upcoming sections. These are the 2 most important performance tests that you may wish to see the results for before your product or application goes live. This is especially true for applications that are connected to the internet.
Load Testing
As the name suggests, in a load test, many users are loaded into the system or application, and then the transactions are performed to see how well they work. Load test gives you an idea of how your application would perform in the real world with “n” numbers of users (referred to as the load) active in the system.
The results of a load test are generally expressed in terms of TPS or transactions per second. This means the system can process “N” transactions per second with an active user load of “X” thousand. The value for “N” and “X” needs to be defined by the business based on the expected number of users and the infrastructure you have in place to handle this load.

Stress Testing
In Stress testing, the system is put under stress and then its performance is measured. It is used to verify the stability and reliability of the system under stress. It is also done to ensure the system does not crash at any point.
Considering your application can handle 1o0 concurrent users. In a stress test, you may start by having 100 or more users in the system performing data transactions. Slowly you would stress the system by either increasing the load or having more transactions performed. Then you would monitor how your application is performing in this stressed situation. The stress test is also performed to understand at which point your system is likely to crash or break.

Major Differences between Load and Stress Testing?
Here are some major differentiation points between load and stress testing.

Sno	Load Testing	Stress Testing
1	It is used to check the performance/functionality of the system under load (multiple active users)	It is used to test the reliability of the system under stress or extreme load
2	The load is set up with multiple active users – virtual or real – inserted into the system	Stress is created by creating more users, data, and transactions in the system
3	Load test helps to identify the upper limit of the users that the system can handle.	A stress test is used to understand the behavior and reliability of the system under extreme load or stress.
4	The performance of the app is measured with load in the system	The reliability and stability of the system is measured under extreme load or stress
5	Some of the load testing tools are Jmeter, NeoLoad, Headspin, Experitest, etc	Some tools recommended for stress testing are Stress Testers, Jmeter, NeoLoad

Examples of load and stress testing
To better understand the difference between load and stress testing, let us look at an example. Let us take an example of an online shopping site. Assuming that your application is designed to handle 1000 concurrent users. When you do a load test, you may want to start with a 50% load. So, you set up your systems to simulate 500 users and then check how the system responds by checking the API response times. If the response time is within acceptable limits, you progressively increase the load to 700, 800, 900, and 1000 to see how your application performs under the different loads.
For the same application, if you were to do a stress test, you will 1000+ users simultaneously generating calling multiple APIs. This will stress out the system which is designed to handle only 1000 users. The reliability of the system is then checked by checking the correctness of the API response, to check if the application or pages crash at any point, the data is saved to and from the database, etc.
Some other examples of load testing are sending multiple files for printing at the same time to the printer, sending thousands of emails at a time to load the mail server, or changing large volumes of data in a word or excel or any other processing system.
Some scenarios that emphasize the need for a stress test are an educational website at the time of result declaration, or eCommerce website during their annual sales or new and anticipated product launches, or the latest vaccination availability and booking apps as well.

Wish to know about the best performance testing tools in the market? Read here!

Performance testing includes various types of testing including Load, Stress, and others. A performance test is done to validate the reliability and stability of the system, ensure the response time is within the defined SLA, and also ensure that the system is scalable.
Load test only concentrates on the performance of the application or system with many active users or with a load. Hence, Load testing can be considered as a subset of the performance test.
What is the purpose of load testing?
The main purpose of Load testing is to understand, how the system would perform under the real-life load. For this, the business first needs to analyze the expected user base for the application. Then a load similar to that number is simulated and the performance of the system is measured. The results are normally mentioned as successful transactions per second under “X” load or “X” active users.
It is very helpful in understanding the achievable performance of business-critical transactions along with resource utilization. Based on the load test result, the business decides to scale up or scale down the backend infrastructure.

What are the different types of load and stress testing?
Load testing can be further divided into 4 different categories based on the load used. These are

Load Testing: Here you simply check the performance of the system under different levels of load which are well within the expected load limits.
Capacity Testing: Also called scalability testing capacity testing is mainly done to identify the maximum load the system and the infrastructure can take without breaking down or without breaching the SLA.
Stress Testing: It is done to find out how the system performs under stress or extreme load. This is achieved by reducing the infrastructure, reducing the database size along increasing the load many folds.
Soak Testing: It is a long-form of load testing where system performance or degradation in performance is monitored over a long duration.

How are load and stress testing done?
Every application or system will have a limit to the load it can handle at a particular time. This limit is decided by the size of the database and servers used. Both in load and stress testing, load or stress in the system is simulated using real users or using tools.
Load testing is done with real users and with simulated users as well. When real users are used, due to the limitation to the number of users available to database, servers, and other infrastructures are scaled down to create a load on the system. Then the testing is performed and the response times are calculated. The results are then extrapolated to derive the performance numbers for the actual infrastructure. When tools are used, any number of users can be simulated, so the actual infrastructure is tested.
Stress testing can be performed only with the help of tools. Here the system is put under stress by having inserting users many-folds than the expected told, or by putting stress on the DB and servers with many transactions and API calls. The aim is to check the stability and reliability of the system under extreme load. It also helps to identify the point at which the system is likely to crash. Based on the results of the load and stress testing, the business may decide to scale up the infrastructure for better application performance and reduced downtimes.
What are the goals of load and stress testing?
The goal of load and stress testing in to find the performance defects in the application and in the infrastructure or network that can affect the application.
The main goals of load testing are:

To ensure that under different permissible the response time for all the transactions is within the SLA (Service Level Agreement) as fixed by the business.
To measure the performance of different application modules under different loads.
To measure the network latency and other components that can impact the response time.
To uncover application design issues that can reduce the performance.
To check the server configurations for web and application to ensure they can handle the load.

The main goals of stress testing are:

To uncover issues that occur only at extreme load conditions.
To check the stability and reliability of the application under heavy load.
To uncover synchronizations issues, memory leaks, and race conditions
Optimizing the system to prevent a breakdown in production.
Planning for the scalability and best utilization of the available infrastructure.

Do you know that volume testing is absolutely needed before app release? Read more

Soak Testing is a type of Performance Testing where the performance of the system under load is analyzed for long-duration similar to a production scenario. Some applications need to be online 24/7 like the eCommerce websites. They may have a different load at different points, a soak test would put the system under test with a specific or varying load and monitor its performance for hours or even days.
A soak test aims to identify issues that occur only after the system has been active for long durations. The most common issue identified in a soak test is related to memory leaks where the system starts degrading after being live for a long time.
Conclusion
The performance of a software application is critical to the success of the application. For this purpose after the functional testing, performance tests are performed. The most common performance tests are load and stress tests. Based on the results of the load and stress test the business decides on the infrastructure needed to support the application.
The load and stress result thus play a very important part not only in the success of the application but also helps business in optimizing resource utilization and improved profit.