Reducing the cost of Automated Testing by building Robust Tests

Matryxsoft Solution team studies and understands the application under test to identify the automation tool which suits best for the application by doing a POC.

  1. Identify the Platforms and Technologies used.
  2. Identifies the Database and the back-end test data
  3. Identifies the controls been used
  4. Works across different testing tools and checks which has the best support to automate tests
  5. Finalizes on the test automation tool

Once the Tool is identified, a forecast on the application study will be done on how and where the development of the software application is moving ..

  1. We study on the progress of the technologies to be used in future and check on the support for the same from the identified automation tool.
  2. Perform an end to end test scenario to see how the controls are been developed and recognized by the automation tool.

Increasing the robustness of the tests

  1. Every application does have custom controls and we make sure to have a permanent solution or a good workaround for the custom classes which acts similar to standard control/classes.
  2. Object Repository will be created and every object will be followed with the standard naming convention and make sure that right attribute is used to identify objects uniquely which may not affect the identification of the same in future development of the application.
  3. Every function written would be parameterized and make sure it is reusable.
  4. Inbuilt utility libraries which are built by Matryxsoft will be an added advantage to the project.
  5. Every Test will retrieve the inputs from a database to make sure change in data will not affect the developed scripts/functions
  6. Regression/Smoke/Integration suite Tests will be grouped to make sure the tests are executed according to the release.
  7. Make sure command line execution will be performed on the suites/tests which helps for CI execution

Increasing the productivity by test management

  1. Automated Project for every build will be versioned using the version control tool.
  2. Every project will be executed using Continuous Integration tool
  3. Every automated project will be bonded to a defect tracking tool
  4. Reports will be generated in an format (e.g. html/xml/pdf) with a high level and a low level reporting structure.
  5. Parallel execution will be supported to increase the performance and reduce the time of testing.
  6. Scheduler will be created for nightly builds.