Please describe ROPARDO testing methodology used in your quality assurance process.
We found our quality assurance process on the “Agile” methodology according to which we develop software in incremental, rapid cycles. This way, interactions between customers, developers and client are emphasized rather than processes and tools. Agile methodology focuses on responding to change rather than extensive planning.
What tools are used?
Our teams use various tools to respond to project requirements of which we mention Microsoft Office, GitHub, IBM Rational Team Concert, Telerik Test Studio, Eclipse Java Neon.
What standard documentations are produced?
- Scope Plan Documentation
- Testing Plan Documentation
- Testing Result Documentation on every Sprint
- Training Plan Documentation in case of knowledge transfer
Please describe your company experience with delivering outcomes using Test-Driven Development and Behavior-Driven Development approaches
By using a Test Driven Development (TDD) we bring into attention if an algorithm works differently than it was intended. This might show there is an actual error in the code, but also that the requirement was misunderstood by the developer. In this situation, Behavior-Driven Development (BDD) will make people talk about the issue and also clarify the scope of a desired feature and fix the code accordingly.
Describing and understanding the needs of a system has a lot of benefits beyond code correctness: establishing dialog and making sure all stakeholders’ concerns are met.
Please describe the Quality Assurance services that you undergo in a software development project.
ROPARDO has dedicated Quality Assurance teams which governs Quality Assurance activities across all projects. They perform adequate testing of all code developed, according to a Test Plan, using pre-defined Test Cases, and generate Software Test Reports.
Our team is familiarized with various testing methods such as:
- Functional Testing – using customized black-box testing, we check if the output complies with requirements;
- Incremental Testing – bugs do not get their way while new functionalities are added;
- Unit Testing – performed by developers through continuous integration mechanisms where test cases are written by the developers themselves;
- System and Stabilization Testing – performed at the end of the development phase and involving complete functional coverage based on the test cases developed earlier as well as load and stress testing;
- Compatibility Testing – ensures that applications are ready to be used on any browser and/or mobile device;
- Integration Testing – performed as part of a continuous testing process during the development cycle;
- Regression Testing – performed per requirements; we will include a round of regressions testing as part of the functional testing;
- Security Testing – ensures applications against vulnerability to virus attacks and unauthorized logins
For each of these testing methods, we provide documented test cases, test plans, and test reports.
What KPI/metrics are used?
Our mature Quality Assurance and Quality Control processes quantify quality of development and release based on various metrics:
- Development Release Quality Index
- Shipped Release Quality Index
- Production Release Quality Index
- Bug Detection Efficiency
You can have the full formulas revealed.
ROPARDO complies with agile practices of continuous testing. In this case, testing happens continuously in parallel with the development process. This helps identifying problems earlier in the development cycle and reduces delays. This type of testing is usually of a functional nature and combines well with unit testing to provide good coverage and minimize regression issues later.
We are willing to customize our Quality Assurance process based on project-specific needs.