Describe about Agile Testing Process Agile Testing

In contrast to most approaches to agile testing,there was no source code available in this environment. Furthermore, a number of contractual frameworks that existed between the vendors involved,and the customer and Scapa, made it highly unlikely that source code would be made available within the timescales of the testing task.

In addition,the majority of issues raised were nonfunctional;that is,they related to performance and stability of servers either under multiuser load or after extended execution. The scope of the functional testing only required consideration of failures that could be detected by gross failure of the application and did not require detailed arbitration of results.

Another key element is timeline; there were twelve applications and the test timeline was twenty person-days (four weeks elapsed). The following conceptual framework was applied to provide a performance model within which tests were defined:

  • The Edge –all systems“break” under sufficient load.System response time increases,the system becomes unstable,or both, beyond sustainable levels when the applied workload(in terms of transaction rates or number of users) is driven above a certain capacity.We refer to the set of acceptable workloads as the working Envelope of the system, and we are concerned with mapping out the characteristics of the Edge.
  • The Signature –systems “break” for a particular reason,and there is a characteristic “signature” of associated system metrics,typically because one or another system resource saturates,serializes,or leaks up to a static limit.
  • Diagnostic transaction set – there is usually a small set of transactions that show a set of differentiated “signatures”;that is,they cause the server to fail for a set of identifiably different reasons.Testing processes can be simplified if they are restricted to these transactions, and it is also possible to work with a test environment that differs from the production environment as long as the same signatures can be detected.
  • Calibration matrix a matrix of factors can be built that maps between the Edges of the Envelopes for the diagnostic transactions on various environments.Simplifications:
  • Since testing is on an exact replica of production,no calibration matrix is required.
  • The edge of the Envelope(and corresponding signatures)is found for a set of “prototypical” transactions whose characteristics are constructed by reference to the architecture,not the business process. A judgment is then made as to how the production workload relates to the Envelope.
  • Clear definition of pretesting dependencies and subsequent close involvement of the customer during testing to address remaining issues as they emerged.
  • The reduction of testing documentation and complexity to a minimum:
  • test plan–standardized across all twelve applications,
  • test case design–standardized across all twelve applications with only detailed application-specific variations,
  • systems performance metric collection–informed and very much constrained by the test case design and standardized across all twelve applications,
  • stress testing and soak testing1 using the same test cases,
  • test summary report–maintained continuously with status updates to the customer on a regular basis,and
  • template-based report for each application issued for review by the customer as the results emerge,followed by full signoff of report set with customer.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

Agile Testing Topics