Today we believe is the high time to open a new discussion section in this blog and share some of our experience regarding independent testing services we have been providing since the inception of Softheme. From the very start of our company we have built a strong QA department with the aim to help our customers bring only high-quality products to the market. Now we can be proud of how this departments develops and the results we keep delivering to our clients.
In the next several posts we would like to offer such information as the description of our testing approach, testing case studies, and samples of testing documentation for your review; and hope that you will find this information interesting and helpful for your business or personal use.
So, here are some words about how we approach software testing in our work:
Why testing with us?
Because we are glad to provide you with a
Process that could be easily customized for your unique needs
- Classic – includes test strategy, test plan, test cases specification, testing reports
- Modern – fast check of the most important scenarios and user routes; testing new/updated modules using checklists and created in-house templates and procedures
Time-proven approach:
- No delays for training and getting up-to-speed
- You pay for actual hours of testing and for bugs found
How we Organize and Manage Testing
Below is the list of activities we undertake to ensure the testing is implemented as required:
- Coordinate the development of test strategy and plan with project holders
- Contribute the testing perspective to other project activities
- Plan the development or required tests; select the required test approaches (test levels, cycles, approach, objectives and incident management planning)
- Analyze requirements and application to be tested
- Estimate the time and efforts
- Acquire the right resources
- Manage the specification, preparation and execution of tests
- Create test specifications
- Prepare test data
- Execute tests
- Document defects
- Run performance tests
- Monitor execution
- Adapt the planning based on test results and progress
- Take actions necessary to compensate for delays
- Measure test progress
- Select appropriate tools; identify where automated testing is needed
- Identify testing environments
- Schedule testing
Test Estimation
To estimate the testing efforts two approaches could be applied:
- metrics-based (e.g. number of test cases, time taken to develop test case and run the test, etc.), and
- expert-based (time required to complete testing identified basing on experts’ experience)
Among things that affect the level of effort required to fulfill the test requirements of a project are: size, complexity of product; timescale and budget; expected amount of errors.
Stay tuned and learn more about our testing approach.
