Login
OpTier
Request Demo »

QA and Application Development

To achieve the optimal user experience, many teams have to work in concert throughout the software development lifecycle. OpTier Business Transaction Management provides a common language for collaboration between the different teams.

 
QA teams and application developers use OpTier BTM to:
  • Ensure that new and changed code is scalable and efficient
  • Optimize code by understanding its behavior
  • Troubleshoot and diagnose code-related issues.

 

 
View response time and CPU usage as transaction throughput increases.
 
The OpTier BTM solution is typically first used to validate non-functional requirements in pre-production performance testing. It complements load-testing tools by:
  • Identifying transaction flows and topologies
  • Detecting performance and time spent on each tier, by transaction
  • Comparing run-time behavior per load, transaction and tier to a baseline
  • Discovering CPU usage and calling ratios (i.e., chattiness) between tiers
 
OpTier BTM enables testing teams to uncover hidden scalability issues before they cause outages in production, and to correctly predict the performance not only of individual applications, but also of multiple applications running together in a multi-tiered, shared environment.
 
Test cycles usually take place under the pressure of tight deadlines. OpTier BTM dramatically reduces problem resolution times, leading to shorter test cycles and successful, on-time application releases. Once the application goes live, OpTier BTM validates the assumptions about usage patterns, volumes, response times, and concurrency. Detailed reports facilitate ongoing validation and communications with application teams and business owners.
 
Solution features for QA and application development
  • Detailed transaction flow in the tested scenarios and their behavior profile across all tiers
  • Cross-tier transaction resource consumption information for creating baselines
  • Transactional information and profiles (such as type of transactions, load, users, etc.) as input for test scripts