Independent QA & Testing

Functional tests

Having proper functional testing ensures that your software does exactly what it is designed to do, which makes it essential for a quality user experience. Functional tests have an important role in this digital world as:

• Simulate the use of the software to discover potential problems before they affect users.
• Locate defects early in the software life cycle to minimize repetition, improve quality, and reduce overall test and development costs.
• Ensure that new features or enhancements do not affect existing software.
• The functionality of the software should be verified within the scope of,
• Unit test / module test: at this stage, we check if the functions of the separate modules are working properly
• Integration tests: at this stage we verify if the functions that involve the interaction of the different modules work as established in their specification.
• System Testing – At this stage, our team carefully examines the functionality of all software as intended, as stated in its specification.

Functional tests are made up of:

• Unit examination
• Integration testing
• System test
• User acceptance test (UAT).

Regression tests

Regression testing is an integral part of every software development process. The regression test is performed after:

• Correct the defects or errors reported.
• Add of new functions in the software.

During Regression Testing, we choose evaluation cases:

• They regularly fail
• They are complex
• Check frequently used functions and main functions.
• Check functions affected by recent code changes – Check limit values
• Check for integration problems, etc.

Because regression tests contain many tests that must be repeated in each test session, they should be automated (if possible). Today, there are several tools available for this, both paid and free.

User interface and usability testing

User interface testing is a procedure to determine if the user interface of a software meets the requirements and is easy and convenient for end users to work with. This type of testing can be performed manually and using various automated testing tools and is carried out in two phases:

• The first is usability testing by qualified test engineers, in which domain experts perform certain tasks as the end user and discover how convenient it is to interact with the software.
• The second is the usability tests carried out by end users: these are the ones who complete certain tasks, the test engineers observe the user behavior, the problems they face when performing the tasks, the way of thinking, the time to understand the interface user name, facial expressions, etc. It is usually used during this session to record what is happening on the screen, the user’s voice, the user’s facial expression, etc. Recordings that are used to discover software usability defects.

Installation test

This is a test that checks the correct installation of the software and how it will function later. It runs when the software is almost ready to go. there are different types of installation:

• Assisted, the user must accept the end user license agreement, select where to install the application, enter the password or activation, etc.
• Unattended, no user interaction required, the necessary parameters are taken from the response file present in the compilation.
• Headless, software installation occurs over the network from one machine to another.
• Automated, the installation is executed when certain predefined conditions are met.

Points to consider during installation tests:

• Memory, how much memory the software requires and if it is within the specified limits.
• Space, the installer checks the required free space in the selected installation location.
• Behavior of the installer in states of non-compliance
• Negative test
• Uninstallation, all the things that need to happen happen.

Load and performance tests

Performance issues are not always due to hardware. Conducting a proper analysis of performance issues can uncover bottlenecks that can occur in software, network, or hardware, and thus produce a software, network, and hardware solution.

The performance tests are composed of:

• Load test, checks if the software works correctly at different load levels and problems that occur during operation with different loads, etc. Defines the normal performance capacity.
• Stress tests, with increasing load, some conditions, factors and an unfavorable environment contribute to degrade the performance of a software. So software should be able to work effectively and efficiently in these circumstances.
• Volume testing, software applications are subject to a large volume of data for processes and operations. It needs that the performance of the software is not hampered while it is fed with a considerable amount of data.
• Reliability test, used to verify the resistance level and the behavior of the system in constant use. Being able to sustain a load continuously for a longer period while maintaining the level of performance imparts the strength and quality of stability of a software product.
• Scalability testing: To meet and adapt to the growing needs of ever-increasing users, software must be scalable to ensure smooth operation. It gives us the option to improve performance beyond specifications.
Security tests

The security testing practice is to search for known vulnerabilities and perform penetration tests to help discover and resolve known security problems. Software security testing is an integral part of the software development process, and network, server, and infrastructure security testing is part of a project’s implementation strategy.

These tests using the appropriate tools, the required knowledge and the necessary capacity are what we offer as a value proposition to our clients. Our comprehensive security testing solution for the application layer, network layer, server layers, and database layer helps protect software from all levels of vulnerabilities and make it piracy-proof.

Our security testing approach provides assurance of compliance with standards, best practices, and regulatory requirements:

• Web Application Security Consortium (WASC)
• Payment card industry: data security standards (PCI-DSS) – International Organization for Standardization (ISO Standard) 27001: 2005.
• Open Web Application Security Project (OWASP) Top 10
• Health Insurance Portability and Accountability Act (HIPPA)
• Sarbanes-Oxley Act (SOX) / Central bank regulations
• Family Educational Rights and Privacy Act (FERPA)
• Data Protection Law and many more …

Main focus for security testing:

1. Injection
2. Broken authentication and session management
3. Cross-site scripting
4. Insecure direct object reference
5. Incorrect security settings
6. Exposure of sensitive data
7. Missing function level access control
8. Cross-site request forgery
9. Use of components with known vulnerabilities: Heartbleed and Shellshock in action.
10. Redirects and Forwards Invalid.

Mobility has integrated new levels of complexity for quality control and test management, for which most companies are not prepared: various technological platforms, operating systems, devices, with different specifications such as screen size, RAM, CPU, etc., numerous use cases, networks. connections and carriers.

Mobile, web, and hybrid applications should be tested in various permutations and combinations. All in cycles more compressed than ever.

We offer you a proven approach to this today’s world problem that covers the full spectrum of mobile testing needs and mobile application behavior in different scenarios:

• Functional tests, functionalities validation, regression tests, offline access tests, negative tests – Non-functional tests: resistance, interruption, network recovery, peripheral tests, different types of networks.
• Interrupt: from SMS, voice, battery / cable removal, notifications
• Memory, its usage, leaks and garbage collection, cache check and data storage mechanism.
• Application performance: CPU usage, network usage, page render time, screen and activity.
• Usability testing: user experience, ease.
• Security testing, OWASP vulnerabilities, static code analysis, and more.
• Localization tests, multiple languages, currencies, time zones, images and text.
• Test installation, uninstallation and updates.

API tests

Today in the world of service-oriented architecture (SOA), it is important that your APIs deliver the expected results in terms of functionality, reliability, performance, and security. Our API testing service makes sure of this, be it API, Web Services or Micro services.

Testing in various browsers

These tests are an integral part of any web application test. Currently there are as many platforms as Windows, Mac, Linux, Android, iOS; in each one there are many browsers such as Firefox, Chrome, Safari, IE, Opera, Opera Mini, UC Browser, Dolphin, Maxthon, Mercury Browser, Nokia Xpress, etc., each browser has different versions. The elements of the web application behave differently in each browser, even in different versions of the same browser, differently on each platform, so it is necessary to verify the combinations to complete the tests between browsers.

We verify the HTML / CSS code in each browser, different dynamic operations performed by JavaScript, alignments, fonts, designs in different resolutions, etc. There are few server-side checks that we need to test how the web application behaves when interacting from various browsers.

Cross-platform testing

These tests are necessary when the software is designed to work on different platforms. Cross-platform tests are composed of:

• Performance tests on each platform
• Security tests on each platform
• Installation test on each platform
• Functional tests on each platform
• GUI / usability testing on each platform
• Location tests on each platform (if necessary)
• Localization tests, globalization.

Localization tests are responsible for verifying whether the software is translated correctly and conforms to local languages ​​and cultures.

These tests should be included in the software testing process when the software is made for more than one language, there should be no wrong translation, missing text, garbled or nonsensical characters. Our role is to take care of verifying the user interface of the software and the text content of each language.

SEO tests

With these tests we check whether the website is search engine friendly or search engine optimized. In the report, we disclose two things:

• A detailed analysis of the current state of the website
• A recommendation to improve the current state.

Due to frequent changes in search engine algorithms, it is advisable to perform SEO tests twice a year to ensure that the website maintains a good position in the different search engines and in this way attracts more visitors and customers. convert into customers.

Due to the increasing frequency of online software updates and new software application release cycles, “Regression Testing Automation” is necessary. Therefore, it must be done in a minimum time and cost.

We have developed a tried and tested approach to test automation that leverages best practices in agile testing, continuous integration, and test-driven development to speed up your QA processes and reduce cycle time.

Automation testing services consist of:

• Assess automation needs.
• Selection of necessary tools.
• Creation of frame.
• Automated creation and execution of test scripts.
• Creation of regression test suites with flexible execution options.
• Training and delivery of the test package for future needs and their maintenance.
• Here are some of the benefits of test automation:
• Reduced cost and time of regression testing
• Faster time to market
• Better quality testing, no human error.
• Improve resource utilization: The QA team can focus more on version-specific functional tests and not repeat the same tests.
• Cross-platform testing: perform tests on different operating systems, devices, and browsers to ensure performance for all end users.

We recommend automating tests that will be run many times over the course of the project; if tests are to be performed only once, automating them is not recommended.