Performance tests

Performance testing, a non-functional testing technique performed to determine the system parameters in terms of responsiveness and stability under various workload. Performance testing measures the quality attributes of the system, such as scalability, reliability and resource usage.

Performance Testing Techniques:

Load testing – It is the simplest form of testing conducted to understand the behaviour of the system under a specific load. Load testing will result in measuring important business critical transactions and load on the database, application server, etc., are also monitored.
Stress testing – It is performed to find the upper limit capacity of the system and also to determine how the system performs if the current load goes well above the expected maximum.
Soak testing – Soak Testing also known as endurance testing, is performed to determine the system parameters under continuous expected load. During soak tests the parameters such as memory utilization is monitored to detect memory leaks or other performance issues. The main aim is to discover the system’s performance under sustained use.
Spike testing – Spike testing is performed by increasing the number of users suddenly by a very large amount and measuring the performance of the system. The main aim is to determine whether the system will be able to sustain the workload.

Tools:

Tests are performed using the “Rebellion” software system, which was created by engineers Sokra-NET. Rebellion in contrast to the known applications of this type, characterized by exceptional flexibility of configuration and the accuracy of the measurement times. During the test, we make the following measurements:

– Total time – total time from the start of the operation (before connecting) to end the call (after completion of receiving data from a web server). All times are counted in seconds to the nearest hundredth of a second.

– Connect time – time to connect (only includes establishing a TCP / IP)

– Pretransfer time – the time from the start of the operation to the completion of negotiations between the client and the server (includes negotiations SSL keys)

– Start-transfer time – the time from the start of operations to send the first byte to the customer

– Redirect time – the time from the start of the operation to the end of redirection (TT corresponds to the action, under which the redirect)

– Datasize – the amount of data transferred in a single operation (in bytes)

– Hits, the number of calls to a particular URL was

Penetration tests

Network Penetration Tests

Penetration testing information systems’ security are intended to show the actual and potential errors in the architecture or configuration; the software and the use of computer networks which can be used by unauthorised people to destabilize the work of the company to obtain confidential information or data modification. For this purpose, the system under the test is subjected to a series of controlled attacks, simulating a real attempt to breach security and stability of networks using the Internet. Generally the attacks use both techniques and programs, and specialised tools. If you detect weaknesses in the system, we are ready to develop solutions for safer alternatives.

Comprehensive penetration tests include:

Tests of existing security firmware
Analysis of software security elements
Web server security tests
Web applications tests
Tests email system
Tests of other available services
Analysis of network architecture and various systems’ paths of access
Tests Denial of Service

Penetration Testing Methodology

Once the threats and vulnerabilities have been evaluated, the penetration testing should address the risks identified throughout the environment. The penetration testing should be appropriate for the complexity and size of an organization. All locations of sensitive data; all key applications that store, process or transmit such data; all key network connections; and all key access points should be included. The penetration testing should attempt to exploit security vulnerabilities and weaknesses throughout the environment, attempting to penetrate both at the network level and key applications. The goal of penetration testing is to determine if unauthorized access to key systems and files can be achieved. If access is achieved, the vulnerability should be corrected and the penetration testing re-performed until the test is clean and no longer allows unauthorized access or other malicious activity.

Offer

Performance tests