Software testing solutions

A software product's quality is one of its most important attributes. In most cases, a product's quality is the single most important factor in a project's evaluation, and with a good reason. Until there is an actual risk of unexpected defects emerging at the users, customer discontent, or the final product simply fails to live up to previous expectations in any way, a project can hardly be considered finished. The product might have already been delivered, but still weighs down those important development and business resources, in addition to boosting the budget allocated to support and warranty services.

As important a software's quality is, dealing with quality factors can prove just as difficult. A typical product is judged by quite a number of people (specialists and users alike) during its life cycle, each representing a different view on quality. More so, when it comes to actual quality measurement, some factors prove hard, and some even impossible to metrify.

Quality Control standards and methodologies deliver the professional perspective and specialist view proven to measure and control the most important quality factors. While the more widely defined field of Quality Assurance covers all activities from design, development, production, installation, servicing and documentation, QC services offered by Newnet are closely process- and product-oriented, making them smoothly fitting with any development or testing project.

Testing in Development

The chief goal of testing is to monitor the implementation of a solution: review software product prior to delivery, with respect to pre-defined quality requirements. The two most important of the aspects examined are: to see that final product conforms to (functional and technical) specifications (verification), as well as to business requirements (validation).

Each of the major tasks in a testing process plays its genuine part in measuring and assuring important factors of quality:

  • Documentation review (requirements, specifications, user manuals).
  • Test planning and execution.
  • Reporting and decision support.

Quality Control methods yield the best results if uninvolved third-party specialist resources are assigned to a development project, and they are assigned early on. Thus testing and development activities are intricately interconnected to complement each other for the best results.

Quality is a goal shared by business, developers, customers, even users alike, with each of them having a different perspective on the project. QC solutions provided by Newnet make sure all of these views are represented in the process of testing as well.

Fields of Testing

Quality Control in software testing extends to all types of applications produced, and can be broken down into nearly as many fields and practices. Our team's testing experience includes:

  • System testing: Functionalities of a new application or new functionalities developed for an existing application can easily have some hidden defects. System testing aims to uncover such defects prior to delivery of the solution. Testing is based on functional and technical specifications, using them as standards for verifying the application.
  • Regression testing: Developing a new version or iteration of an application might violate existing, proven functionalities as well. Regression testing reviews if fundamental and other impacted functionalities are intact and operating correctly.
  • User acceptance testing: Acceptance testing aims to review if delivered application conforms to defined business requirements as planned. Acceptance tests are performed by the user (customer), testing team's role is to prepare, organize, and support the process.
  • Post-production testing (on-going support): Makes sure that instant bug fixes work properly in test environment before they make their way into production. Its goal is to help avoiding damages a non-working or disfunctional patch could deal.

Note that in the majority of cases a project calls for including all of the fields above, but each of them can be made use of as a distinct methodology if needed.

Skills, Tools and Testing Experience

Newnet team of testers employ well-proven processes based on actual professional experience, constantly revising, updating, and flexibly adapting these methods to meet our partner's requirements and standards. We aim to provide a wide scope of IT competence with an extensive knowledge in specialist fields, returning maximum results for optimal expenditure.

Skills and abilities of our specialists include:

  • fine analytical prowess
  • cooperative, customer-oriented mindset
  • a good command of English
  • well-founded skills in SQL (test data retrieval & preparation)
  • experience in test automation

Main tools used to support the testing process:

  • HP (previously: Mercury) Quality Center applications
    • Test Director for Quality Center
    • WinRunner
    • Quick Test Professional

Experience in testing extends to

  • platforms and standards
    • Microsift .Net, J2EE
    • MS SQL, Oracle
    • BEA Tuxedo
    • Vitria BusinessWare
    • XML, XSLT
  • applications
    • stand-alone applications
    • integrated solutions running in corporate environments
      • CRM systems
      • self-care systems (Web, IVR)
      • on-line retail solutions
      • AMDOCS billing solutions

Why Testing is Important

Expenses of a testing project can be broken down to exact amounts. On the other hand, the costs of warranty services or damage dealt by unforeseen defects of a product can not be reckoned with beforehand. What is more, these figures might frequently be accompanied by an additional grave loss of reputation.

Development without testing:

  • No feedback on the development process.
  • No proper information on the quality of delivered application.
  • Serious defects discovered by user / customer following final delivery is a major risk.

Development augmented with testing:

  • A good impression of
    • the overall quality of the development process
    • possible risks and shortcoming
    • improving the process
  • Provides an objective and comprehensive image of the application's quality preceding actual delivery.
  • A decisive number of defects can be found and fixed during the development period.

The later a defect emerges, the more it will cost to fix it; expenses for correcting defects discovered during testing and development are significantly lower.