SQ72 Software Quality Assurance Practices

Software Quality Assurance Practices

SQ72 evaluate how a system performs in terms of responsiveness and stability under a particular workload based on real operating conditions. Performance tests are required to quantify and benchmark speed, robustness, reliability, and application scalability. Performance tests should be conducted as early as possible and should focus on software components such as web services, microservices and APIs.

The earlier the components of an application are tested, the sooner any performance anomalies can be detected which ultimately reduces the time and cost to fix them. Tests should also be conducted regularly so that performance trending data can be understood and factored into the engineering of the final software product.
We specialise in robust system and software application Performance Testing! We will performance benchmark your applications, ensuring that you have the right inputs to create the best possible end user experience, ensuring that your software is responsive to the needs of it’s intended audience at all times!

Software Quality Assurance Consulting Services

Software Quality Assurance (SQA) is not the same as Software Testing! Effective SQA prevents defects and is driven by the entire Organisation’s Culture! SQ72 is the only company to address effective software quality assurance through addressing the culture of the organization. A culture of quality excellence prevents 80% of software defects before they enter the coding process. It addresses the whole software value chain in the organization, Business and IT and therefore cannot be driven by the Test Team! A critical component in delivering near defect-free software releases is to ensure that all stakeholders, processes and policies work in an effective and efficient manner and have all been executed with the quality of the end product in mind. This requires effective quality gates throughout the entire software creation value process. This means regular and effective communication channels and a sense of maturity and ownership of quality from all stakeholders in order for the creation processes of quality software to happen seamlessly and automatically.
For example: If a defect is detected and eliminated in the requirements phase, it may take an hour to remedy. If a defect is detected in production, it typically takes 55 hours to remedy and the impact of that defect in production could result in massive risks to the clients from a business continuity perspective, potentially damaging the brand. This alone should be enough motivation for all teams and individuals to adopt a quality mindset to their individual tasks, whether willingly or forced via the implementation of quality gates.

Quality Gates represent:

  • Formal checklists are used throughout the life of a project.
  • Formal sign-off and acceptance occurs at each gate.
  • Assessment of the quality and integrity of the product takes place.
  • Information is assured to be communicated to the correct stakeholders (i.e., deployment hands off to operations, etc.)

Some of the benefits of effective quality gates are:

  • Detection and resolution of defects as early as possible
  • Prevention of most defects entering into the development and testing phases
  • Elimination of most redevelopment and retesting due to defects
  • Greater understanding and ownership of quality from all teams and stakeholders
  • Fewer defects in productions
  • Fewer calls logged to the service desk due to defects
  • Shorter time to market for software changes.
  • Decrease in associated costs due to elimination of rework
  • Better quality software builds released into production
  • Improved levels of reporting to the business through effective quality practices
  • Greater confidence in the ability to make quick software or infrastructure changes that does not impact the business or clients
  • Effective collaboration and communication across all stakeholders.

Quality Gates in a DevOps environment: