Which is better automation testing or support

Automation tests with LoadView

Automation tests consist of special tools that are almost always separate from the software under test. It works to control the execution of tests and to be able to make a comparison between the results obtained and what is expected of them. For test runs, we can incorporate repeated and necessary tests into a formal testing process that already exists, or add tests that are difficult to execute manually. The following are the general approaches that are typically used for automation testing.

Code or code driven tests: Public interfaces of classes, modules, or libraries are tested with a variety of input arguments, and the results obtained are validated as expected.

User interface tests: A test framework generates a series of user interface events, such as: B. Typing, clicking and other interaction with the software, and resulting changes in the user interface are observed to check whether the behavior of the observable program is correct.

In the case of LoadView, it is a performance test solution that allows users to run a variety of stress or stress tests or test types, such as: B. the creation of these at the beginning and everything in our LoadView web tool, from performance or load tests, application tests, but also to be able to carry out and create tests of, such as unit tests of web services, or comparison of the results for regression tests. Etc.

Automation Testing: LoadView Benefits

The process of using this solution complies with the quality regulations in terms of operational, easy understanding and has a fairly broad and descriptive knowledge base, something very positive that helps during the process is the immediate response through chat to needs for any doubts about the technical Supporting areas that respond clearly and effectively to any confusion is beneficial as it allows faster progress with the installation, customization, optimization, and execution of the tools. LoadView offers significant advantages in integrating and automating our tests:

  • Users have full control over the final cost of each test and multiple test types to choose from when running their tests.
  • Platform or interactive portal of the latest technology.
  • It allows to create very complete tests of performance, as well as automate, create and edit monitors that can run for a long period of time, and configure these alarms and actions before errors or errors in the test load.
  • It has one of the most comprehensive script recording tools out there. Not only does it perfectly capture all the scripts that are running at the moment, very quickly, but it also allows you to run web image tests! This last functionality perfectly captures any area or frame or image that you want to test and should always be displayed on a webpage, which is a great benefit and makes it much easier to do front-end testing and web design.
  • Full integration with multiple and critical tools to optimize and automate CI / CD tests like Jenkins, third party services like Azure, Slack and repositories like Github etc.
  • Most importantly, it allows us to run tests in messaging formats like SOAP and REST, which are messaging companies that work with the largest number of companies worldwide in terms of web service, even integrating with customers using AWS or enable cloud-based services such as AZURE.
  • Since it is developed with the latest technologies in mind, this allows integration with almost any system of any customer, at least those working with not-so-obsolete technology.
  • Direct email reports can be configured for each execution, reporting the beginning and the end of each process, with their respective results at the moment, which is a very important functionality for important companies like banks, insurance companies, etc.

Among many other benefits, you'll find a wide range of features and benefits with LoadView.

 

Automation tests: test case

For our test automation case, we'll use Jenkins for our sample case. The integration with Jenkins is very simple, we just need the latest version of Jenkins, a tool to create projects and scripts and finally a .war file where we will run the Jenkins from our local host. We'll also be using the EveryStep Web Recorder to script a series of steps a CPA would consult on an Argentine mail website.

 

Step 1. Create a new web API test integration. Account integrations Add Integration Load Testing Web API as shown>> in the image below.

 

step 2. Download and install the LoadView plug-in for Jenkins.

 

step 3. Once the Jenkins plugin has been installed and customized on your local host, the LoadView credentials must be registered in order to proceed with automating tests > Credentials Add Credentials> LoadView Security Token (UID). In the UID field you have to use the first step password that you made.

Step 4. After completing the previous steps, let's configure our test scenario. In this case, it is an integrated web application test that is carried out with the EveryStep Web Recorder. There are a few fields that require you to enter certain test settings.

  • Scenario ID. Paste the test scenario ID that you want to use in the build. You can copy the ID from the scenario page in LoadView.
  • Failure threshold. Here you can specify an acceptable percentage of sessions with errors that occurred during the test (unable to access the target resource, no keywords / image found, etc.). If the percentage of error sessions is greater than the specified value, the build is marked as an error in Jenkins.
  • Average time. Specify a limit for an average response time measured during the test execution. If the limit is reached, the build will be marked as an error in Jenkins.

 

 

Once we get to the final integration, it would look like this:

In the latter case, the test is in an error state or fails because, in order to establish the satisfactory connection between LoadView and Jenkins, the IP is currently available and registered in a whitelist that allows you to end the web integration process and view all functions, since the results for each design or execution are displayed satisfactorily.

 

Automation tests with LoadView: conclusion

For this example, we created our test from the use and integration with Jenkins Test Automation Server Case shown in the previous topics, where we perfectly capture the script that runs when we consult a CPA on an Argentine mail website . Once the test is complete, you can find the summary results at LoadView results in the Jenkins build menu. To review more comprehensive LoadView reports on the test execution details, select more detailswhich shows the full summary of the test, including the execution plan, average response times, session information, and any errors encountered during the test. For more information on LoadView and LoadView integration with Jenkins, see our Knowledge Base article.

Get started with LoadView for free and get $ 20 in load test credits.