Risk based Software testing is critical to software quality assurance that represents the ultimate outcome of the reviews during the software life cycle i.e requirement specifications, design and software development. At General Softwares, we ensure the entire aspect of the system for verification and validation before certifying the readiness for the end users.
Key Testing Methodologies
| White Box Testing | Black Box Testing |
| It focusses on the program control structure, wherein the test cases are derived to ensure that all statements in the software program have been executed at least once during the testing and all the logical program flow conditions have been exercised and rectified for error conditions. | The black box testing ensures a thorough validation of functional requirement from end user's perspective, without the regard to the internal workings of the software program.
|
What is it? During the entire life cycle of software development process, there are numerous sources of injected defects, that pose risk of potential failure of software to function as expected. Right from the requirements, design and source code generation, it is extremely essential to thoroughly ensure the quality standards by testing at every step of development, thereby uncover and correct/rectify as many errors as possible before delivering to end users. There are several well defined software testing techniques that provide systematic guidance to design and execute tests for (1) verifying the internal logic of software components, and (2) validate the input and output domains of the software program to uncover defects/errors in functionalities, behaviour and performance. Therefore the Software Quality Assurance (SQA) consists of a well defined means as per the agreed plan, of monitoring the software engineering processes and methods used to ensure quality.
Who does it? During the initial phases of software life-cycle, a developer, business analyst can perform the tests. But, as the software evolves and incorporates the complex components, we assign a team of software testing specialists, right upto the final implementation for client use.
Why is it important? As you would agree, that customers (end users) tend to dis-approve the software that doesn't meet their minimum expectations in terms of its functional and performance standards. General Softwares understands this risk of unacceptance, and therefore ensures your software is rigorously tested upto an acceptable level of risk using high level of quality standards, before putting before your customers. The main objective during SQA cycle is to uncover highest possible number of errors, systematically using disciplined techniques.
What are the steps in software testing?
- Traceable to customer requirements.
- Planned well before testing begins - approved Test Strategy.
- Applying Pareto principle (80% of errors are likely to traceable to 20% of software components).
- Begin in "small steps" and progress towards testing "in large".
- Conducted by an Independent Software Test Specialist team.
Testing = Verification + Validation
Testing is the base of quality assurance for the software; testing is base on static analysis and dynamic analysis. Static analysis is to check source code off line to optimize and coding standard applied on the software, without running the program. The dynamic analysis is performed by running the application and checks all the functionalities with real data and output. A good testing combines both static and dynamic analysis for the quality testing of the software. We deliver high application after thorough check quality and testing. Quality assurance is a process-driven approach with specific steps to help define and attain goals. This process considers design, development, production, and service.
Software Testing Techniques