/ PT / ES / EN /

Quality Assurance

Continuous quality assessment and improvement in delivery is essential for an efficient IT. Quality assurance should be proactive and focused on real results for the business. Over more than a decade, we have acquired a broad practical experience that has been consolidated into several practices.

WHAT IS IT?

Defining, structuring and creating programs for automated execution and validation of functional and non-functional testing

WHAT IS IT FOR?

  • Performing successive series of the same tests and ensuring that the environment’s behavior is as expected.
  • Ensuring that the behavior is the same in different environments, whether in testing, approval or production.
  • Running a large number of validations in a short period of time.
  • Making complex validations with a large set of results, such as batch meshes.
  • Sequencing the execution of several tests for validating the overall behavior of the system.

RESULTS

  • Surveying the set of programs be executed in an automated manner for validating the environments.
  • Consistent recording of results – tracking.
  • Recording defects or incidents using the proper tools, with the ability to identify and reproduce the detected flaws.

TIMEFRAME

1-3 months.

WHAT IS IT?

Identification and resolution of application bottlenecks. It is done by applying synthetic loads on the environment and monitoring all of the infrastructure components (Web server, application server, database, operating system, storage and network). It issues a report indicating the volume of concurrent users supported by the environment, as well as volume and response time of executed requests and transactions (throughput).

WHAT IS IT FOR?

  • Testing application behavior under a high user or data volume situation
  • Mapping application performance in a new environment.
  • Identifying application bottlenecks
  • Measuring the application’s capacity before it goes into production, and correctly size the resources required for its use.

RESULTS

  • Prevents and corrects deficiencies before they affect end-users.
  • Scales resources for the proper functioning of the application in production.
  • Anticipates the impact of growth on the application’s behavior.
  • Assists project implementation decision-making (GO/NO GO) in CABs.

TIMEFRAME

2 to 6 weeks. It can also be done within the production environment in a variable period.

WHAT IS IT?

Controlling and generating mass data used in testing procedures. It enables executions to be done consistently and coherently across multiple test environments. It has a map of how the information should be generated and maintained within the environment. It provides creation, maintenance and aging activities for the mass data.

WHAT IS IT FOR?

  • Providing information so that tests can be carried out in the environment.
  • Preventing teams from having to stand by and wait for information for them to be able to work.
  • Maintaining the structured knowledge about the mass data generation and maintenance
  • Serving as a central point of knowledge for the multi-system teams.

RESULTS

  • Accelerates the testing process with the advanced creation and maintenance of the mass for executing the tests.
  • Reduces system operational risk while maintaining a knowledge base that can be used by several teams.
  • Prevents wasting of development and testing teams’ time.

TIMEFRAME

3-6 months to start operations.

WHAT IS IT?

A support for structured test processes that includes continued monitoring of environments used for testing, incident management, configuration management and component promotion between environments in a controlled manner, synchronized with the teams.

WHAT IS IT FOR?

  • Managing test, type approval and pre-production environments shared among different projects.
  • Integrated and complex test environments.
  • Ensuring maximum environmental availability and stability for validating applications.
  • Increasing the efficiency of test teams and eliminating test inconsistencies.
  • Improving the monitoring of the development project evolution.
  • Restoring the environment as quickly and assertively as possible.

RESULTS

  • Increasing environment availability by up to 2x, increasing the testing period.
  • Cost reduction in validation team rework.
  • An 80% reduction in the incident resolution time.
  • Generation of a knowledge base of known incidents and workarounds.
  • Effective component versioning control in each environment.
  • Promotion windows implemented in non-production environments.

TIMEFRAME

1-3 months.

WHAT IS IT?

Assessment of the pros and cons of the architecture of an application under development. It identifies architectural deviations, or deviations in code building and architecture standards that impair performance requirements, or that could produce side effects such as difficulty and complexity in maintenance, fragility and single failure points, lack of redundancy in sensitive and critical components, and low scalability. All architectural documentation artifacts, which also involve non-functional aspects of the application, are analyzed.

WHAT IS IT FOR?

  • Analyzing critical applications under construction, ideally in the early stages of the project, when the requirements and scope are already set but the technical design is still being produced.
  • Increasing code efficiency when the first components of the application are being built.

RESULTS

  • Anticipation of architectural and coding problems.
  • Detailed report presentation with identified problems, predicted impacts and recommendations.
  • Drastic cost reduction in applications which construction would occur under inadequate architectural fundaments.
  • Improved training of the architecture and development team.

TIMEFRAME

2 to 3 months for architectural analyzes. The results can only be obtained after the construction itself of the application, which could take months or years.

Especialista

especialista@inmetrics.com.br