Exploratory testing is a results-oriented process. It is complete once deliverables are produced that meet the specified requirements. It is especially important for the test results to be repeatable and defensible for certification. As the tester, we must be prepared to explain any aspect of our work to the client, and show how it meets the requirements documented in the procedure. A test plan automates the testing process and further ensures results should be verifiable and repeatable.
Improper testing will cost you money!
There are many risks associated with not testing properly. We have attempted to list some of the more obvious risks below:
Without a properly designed test plan you may even neglect to test a portion of your software.
Failure to design a proper test plan could lead to allocating precious resources to items that have a lower priority, or even worse, not allocating enough towards items that are critical to the success of the project.
If you are using the waterfall approach and you leave the testing until the end of the project, you may find that a significant problem could cause you to have to redesign the entire project.
The cost of finding and fixing bugs increases as the software development lifecycle goes on.
Top
Different tests use different dimensions, or characteristics, to measure product quality. Here are some of the tests that we perform. We will add customized tests to meet your specific requirements.
We analyze every new project at Futurism to ensure that we have fully understood its requirements. We want to prevent any surprises. Our team of qualified, experienced engineers has extensive experience in this demanding area.
One of the business problems that software platform vendors face is how to efficiently and accurately test their products, while at the same time delivering products on schedule. We address this challenge by developing test automation and its associated test harnesses and drivers, using third party automation tools.
We have extensive experience in working with a variety of tools, such as Rational Robot, Segue's Silk Test, Mercury Imperative's Win Runner and Quick Test Pro, Rational Visual Test, etc.
It may be advisable to supplement automation with manual testing (or vice versa). We can help to determine which portions of the application or service can be effectively automated, and which are best left to manual testing. After thoroughly understanding the product under test, and analyzing our client's testing requirements, we develop the test cases necessary to ensure that all components of the product are covered in all aspects, incorporating any test cases that the client may already have prepared for automation.
Quality Assurance Plan and Quality Test Plan are prepared at the launch of the project. These plans outline all the activities to be performed to meet the quality objectives from the customer's perspective. It is the respective test lead's responsibility to ensure that all quality system procedures/standards applicable to the project are followed, and that all the tests and reviews are conducted in a planned manner. Risk analysis is done.
SQA audits are carried out to evaluate the progress of the project and ensure that every project meets the limits that are defined at the organizational level.
It involves following activities:
Preparation of Software Quality Assurance Plan
Approval of plans
Recording and resolution of problems
Necessary focus on measures of quality
Quality performance check
A continuous quality performance is measured in terms of:
Number of reviews and inspections conducted
Number of errors detected and phase of detection
Number of customer complaints
Number of NCs (Non Conformances) reported during audit
Review Effort
Defect Detection Efficiency
In-process defect density
Delivered defect density
Maintaining history of all above documents.
DOCUMENTATION & REPORTING
A project's software quality requirements determine what data must be collected, analyzed and reported. During the design phase of the software, project management should set software quality metrics, based on the software quality requirements described in the SRS
Some common examples of QA processes are:
Code Coverage
Defect distribution and density
Defect trend analysis
Mean time to discover next - faults
Mean time to failure
Mean time to recover
Failure analysis
Root-cause analysis
Quality gap analysis (release criteria vs. actual test status)
TESTING CYCLE
The best approach to testing is to start with basic functionality and gradually add levels of complexity at each successive stage. As each test is completed, the results should be documented and verified against the project requirements. Any problems should be investigated and resolved. We follow the above well-documented testing model for our client testing. We can plug into your testing cycle at any stage.
Unit Testing
Unit testing consists of a focused set of tests that specifically target a single operation, function, or process. The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as you expect. Each unit is tested separately before integrating them into modules to test the interfaces between modules. Unit testing has proven its value in that a large percentage of defects are identified at a stage when fixing them is relatively inexpensive.
Parallel/Audit Testing
Testing where users reconciles the output of the new system to the output of the current system to verify the new system performance the operations correctly.
Functional Testing
Black box type of testing geared to functional requirements of an application.
Incremental integration testing
Continuous testing of an application as new functionality is recommended. This may require various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers are developed as needed.
Integration Testing
Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. A component, in this sense, refers to an integrated aggregate of more than one functional unit. Integration testing identifies problems that occur when units are combined. By using a test plan that requires you to test each unit and ensure the viability of each before combining units, you know that any errors discovered when combining units are likely related to the interface between units. This method reduces the number of possible causes, permitting a far simpler level of analysis.
System Testing
A type of testing to confirm that all code modules work as specified, and that the system as a whole performs adequately on the platform on which it will be deployed. Testers, who are trained to plan, execute, and report on application and system code performs system testing. They are aware of scenarios that might not occur to the end user, like testing for null, negative, and format inconsistent values.
Acceptance Testing
Formal testing conducted to determine whether a system satisfies its acceptance criteria and thus whether the customer should accept the system.
Sustained Engineering
With an ever-changing technological landscape you need a strategic edge in the form of Sustained Engineering Services to emerge as the leader. But with your resources locked into maintaining existing product-lines, you have limited time and energy to devote to productions your vision into a product targeted for future release. With Futurism taking care of your non-core testing requirements, your company's in-house QA team can focus on its core functions.
Regression Testing
Any time you modify an implementation within a program, you should also do regression testing. You can do so by rerunning existing tests against the modified code to determine whether the changes have broken anything that worked prior to the change, and by writing new tests where necessary. Regression tests should include tests written to verify bugs that have been fixed during the product cycle. Adequate coverage without wasting time should be a primary consideration when conducting regression tests.
Alpha Testing
Testing an application when development is nearing completion. Minor design change still is made as a result of such testing. The end users or others typically do alpha testing.
Beta Testing
Testing when development and testing are essentially completed and final bugs and problems need to be found before the final release. End users or others typically do beta testing.
Top
Within Methodology
Back to "