|
|
|
Case Studies |
Testing of Database Security System |
|
Duration: 9 months
Team size: 10 persons
Large scale testing project included some subprojects both of them were used Automated Testing Lifecycle Methodology (ATLM).
The first subproject was focused on development of automated testing scripts and fulfillment of complete testing of a special tool. This tool was aimed to create connections with predefined sets of databases, to transmit data in a batch mode, to log the results in Database security system and to run the set of available commands.
|
|
 | Performed testing |  |
|
Manual and Automated Functional testing (more than 3k Test Cases)
Automated regression testing
Bugs and Enhancements Reporting
Business cycle testing
GUI testing
Performance/Load testing | |
 | | |  |
|
|
|
This subproject included the following phases:
Establish Test Strategy and Test Plan
Design manual Test Cases for Functional, Business Cycle, Performance, Volume and Stress testing
Perform manual testing and record results into Test Protocols. Fill all found defects in bug tracking system
Automate Functional, Performance and Business cycle tests using Jmeter as the basis
Run and debug Automated tests, compare the results to results of manual testing (in order to verify correctness of scripts)
Create documentation how to use Automated tests for Automated Regression testing
The goal of the second subproject was comprehensive testing of one module of DS System. This module with web interface is used for audit and monitor privilege setting changes in selected databases, sending alerts to authorized users about the changes. Testing was performed for main platforms and following databases: Oracle, MS SQL Server, DB2/UDB, Sybase, Hi-RDB.
The subproject included the following phases:
Writing Test Requirements and manual Test Cases in Quality Center (~2k test cases)
Performing manual testing and record results into Test Protocols. Filling of all found defects in bug tracking system
Creating Test concept and Test Engine in order to raise effectiveness of testing and provide reuse of common actions of each test
|
|
|
Without Test Engine productivity was up to 2 Tests/PD, with Test Engine – about 20 Tests/PD. Test Engine used MS SQL database for common and particular Test Parameters for each test. After creating of Test Engine there was no need in high qualified developers for writing of Automated tests.
Creating Parameters for all Automated tests
Running and debugging Automated tests, comparing the results to results of manual testing (in order to verify correctness of scripts)
Creating documentation on usage of Automated tests for Automated Regression testing
|
|
|
Testing of Namos Compact
Duration: 24 months
Team size: 3 persons
NAMOS compact is an integrated POS, payments and shop item management system for the service station segment. NAMOS compact contains two software packages:
|
|
| |
|
|
|
Testing of RAD Platform
Duration: 18 months
Team size: 4 persons
Specialized RAD platform designed as multi-tiered framework providing building Business Applications of new generation. For this project incremental development lifecycle model is used with multiple deliveries.
|
|
| Tools used | |
|
JUnit – used for Unit testing
Canoo – used for Load and Performance testing
Load Test Runner – own tool is used for Load testing | |
| | | |
| |
|
Currently the testing process accomplished by regular executing 400 junit tests, 400 automated scripts, and 1200 functional tests. |
| Performed testing | |
|
Test Types\ Test Levels |
Unit |
Issue |
Integration |
System |
Ad Hoc | | | | |
Functional | | | | |
Performance | | | | |
Load | | | | |
Volume | | | | |
Stress | | | | |
Installation | | | | |
Configuration | | | | |
Security | | | | |
Reliability | | | | |
Usability | | | | |
Business case | | | | |
Regression | | | | |
| |
| | | |
|
|
|
|
|
|
