Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Less14 3 e_loadmodule_4


Published on

This is part of R12 Testing Suite for Oracle Applications or E-Business suite.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Less14 3 e_loadmodule_4

  1. 1. Reports & Graphs Introduction to Oracle Application Testing Suite: e-Load
  2. 2. Reports & Graphs <ul><li>Generates Graphs and Charts to help analyze potential bottlenecks </li></ul><ul><li>Allows you to chart historic test data with recently executed test data </li></ul>
  3. 3. Reports & Graphs
  4. 4. Session Report <ul><li>Session report is an overview of the test </li></ul><ul><li>May be exported to a CSV file for portability and distribution of results </li></ul>
  5. 5. Create Graphs <ul><li>Provides solid data for later use regarding the last test </li></ul><ul><li>Provides statistics for Script Execution Times </li></ul><ul><li>Provides metrics such as the following: </li></ul><ul><ul><li>Total Virtual Users </li></ul></ul><ul><ul><li>Transactions (Script Executions) per Second </li></ul></ul><ul><ul><li>Pages & Hits per Second </li></ul></ul><ul><ul><li>Total Transactions Executed </li></ul></ul><ul><li>Contains last executed Virtual User configuration </li></ul>
  6. 6. Create Graphs <ul><li>Click on New Graph to generate a new graph </li></ul>
  7. 7. Create Graphs <ul><li>Filters let you select which Data Series to plot on the graph </li></ul>
  8. 8. Create Graphs <ul><li>You can save the graph in various formats </li></ul>
  9. 9. Performance vs. Time <ul><li>Performance vs. Time: </li></ul><ul><ul><li>Gives script completion times during the total test execution. </li></ul></ul><ul><ul><li>This trend should remain flat unless a defect occurs within the web application. </li></ul></ul><ul><ul><li>A bottleneck will cause performance time (script completion times) to increase </li></ul></ul><ul><ul><li>Invalid server responses may cause decreases in performance times. </li></ul></ul>
  10. 10. Performance vs. Time
  11. 11. Errors vs. Time <ul><li>Errors vs. Time: </li></ul><ul><ul><li>Number of errors encountered at the time of execution </li></ul></ul><ul><ul><li>Should always remain at zero. </li></ul></ul><ul><ul><li>Occasional spikes mean occasional failures. </li></ul></ul><ul><ul><li>Increasing spike frequency over time may indicate that the server cannot withstand the existing load without throwing an error. </li></ul></ul>
  12. 12. Errors vs. Time
  13. 13. Errors vs. Users <ul><li>Errors vs. Users: </li></ul><ul><ul><li>Same as “Errors vs. Time” except that the graph is plotted over the total number of users run during the test. </li></ul></ul>
  14. 14. Errors vs. Users
  15. 15. Performance vs. Users <ul><li>Performance vs. Users: </li></ul><ul><ul><li>Shows script completion times given vs. the total active users. </li></ul></ul><ul><ul><li>Graph should remain flat unless a defect occurs within the web application. </li></ul></ul><ul><ul><li>A bottleneck will cause performance time to increase. </li></ul></ul><ul><ul><li>Invalid server responses will cause the performance time to decrease. </li></ul></ul>
  16. 16. Performance vs. Users
  17. 17. Statistics vs. Time <ul><li>Statistics vs. Time: </li></ul><ul><ul><li>Shows Kilobytes/Second, Transactions/Second, Pages/Second, and Hits/Second. </li></ul></ul><ul><ul><li>As users continue to increase, KB/Sec should increase. </li></ul></ul><ul><ul><li>If KB/Sec remains does not increase given increasing users, there may be a an issue with the application keeping up with the load applied. </li></ul></ul><ul><ul><li>If KB/Sec decreases given increasing users, a bottleneck may exist. </li></ul></ul><ul><ul><li>Heavy KB/Sec fluctuations may indicate unstable servers given the current load. </li></ul></ul>
  18. 18. Statistics vs. Time
  19. 19. Statistics vs. Users <ul><li>Statistics vs. Users: </li></ul><ul><ul><li>Same as Statistics vs. Time but potted over the actual number of users run during the test. </li></ul></ul>
  20. 20. Statistics vs. Users
  21. 21. Support <ul><li> </li></ul>