Our test strategy

Our Mission

Our testing strategy consists in

  1. Helping customers to get better sofware with higher quality and reliability.
  2. Reducing costs and Time through prenventing and finding early critical bugs.
  3. Managing risks by running important tests that relate to key quality risk. Hence, the main is to reduce the quality risk to a known and acceptable level prior to release.
  4. Providing the project team with important information about quality, testing, and readiness to release

Test Approaches

Our Test Team follows an analytical test strategy (requirements-based testing and risk-based testing). As a matter of fact, they need it when they analyze the test basis to identify the test conditions to cover.  Thus, Improve Software Testers can also derive test cases from their paractical experience and using reactive techniques like test exploratory and error guessing.  If needed, our testing teams can participate in all testing levels in order to reduce regression averse. Besides, they get better ROI by using Test Automation.

Test Levels

Unit Test: It is used for Agile methodology. Since code changes continiously. Our testers automate component regression tests in order to be confident that changes have not broken existing components.

System Test: Testers relocate to permises in order to verify whether the software performs in confirmity with the requirements.

Thanks to their good command of bug tracking systems and test management tools, our testers are able to improve your software.

Defect Classification

  • Major: A defect that results in software failure.
  • Minor: A defect that does not cause a failure during software use. 
  • Fatal: A defect that results in an abrupt crush of the system.

Entry Criteria

The entry criteria (called definition of ready in Agile development) define the preconditions so that to undertake a test activity.

Typical entry criteria include:

  • Availability of testable requirements, user stories, and/or models.
  • Existance of test items that have met the exit criteria for any prior test levels
  • Accessibility of test environment
  • Availability of necessary test tools
  • Availability of test data and other necessary resources

Exit Criteria

Exit criteria (called definition of done in Agile development). Conditions must be achieved so as to declare a test level or a set of tests completed.

Typical exit criteria include:

  • Execution of planned tests
  • Definition of  level of coverage (requirements, user stories, risks)
  • Limitation of unresolved defects
  • Achieving levels of reliability, efficiency, usability, and other relevant quality characteristics.

Testers Profiles

Test Analyst: works on risk-based testing established by the Test Manager. He contributes his knowledge such as risks related to safety, business and economic concerns.

Test Manager: responsible for testing and evaluating a test object and directing, controlling in addition to administrating plans. He is also responsible for test object evalution.

Mobile Tester: has capabilities for testing specific characteristics: security, usability, performance, compatibility and reliability.

Automation Tester: uses software to perform test activities, such as test management and test design, test execution in addition to results checking.

Tools

  • Jira
  • TestLink
  • Firebug
  • Bugzilla
  • Mantis Bug Tracker
  • Occygen
  • Zephyr
  • Squash TM
  • Xenu’s Link Sleuth
  • Jenkins
Talk To An Expert
Automation Testing
Mobile Testing
Web Testing
Live Chat