1 / 18

Testing CIS 726

Testing CIS 726. Karl D. Remarais & Karthik Gundimeda. Software Testing can be stated as the process of validating and verifying that a software program: meets the business and technical requirements that guided its design and development; works as expected; and

hachi
Download Presentation

Testing CIS 726

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TestingCIS 726 Karl D. Remarais & KarthikGundimeda

  2. Software Testing can be stated as the process of validating and verifying that a software program: • meets the business and technical requirements that guided its design and development; • works as expected; and • can be implemented with the same characteristics. It is commonly believed that the earlier a defect is found the cheaper it is to fix it. Software Testing

  3. Unit Testing • Integration Testing • Regression Testing • Acceptance testing • System Testing • Performance Testing Testing Levels

  4. Traditional CMMI or waterfall development model • Agile or Extreme development model The Testing Process

  5. Unit Testing - JUnit, CppUnit, NUnit, etc... • Performance Testing – Jmeter • Acceptance Testing – Fitnesse • Functional Testing (UI) – Selenium • Regression Testing – CruiseControl • Integration Testing - Ant, NAnt, Make, etc... Testing Tools

  6. Unit testing with code coverage using EclEmma • Integration testing/ black box testing of each module • System testing • Performance testing • Comments and suggestions from the team members Applying testing methods to the project

  7. Verify the functionality of each method in a given class by coding one or more test case for each public method. • Use EclEmma to check that we have 100% of code coverage. Unit testing with code coverage using EclEmma

  8. Verify that each module of the system works properly and are producing the expected values for a given input. • Database and persistence layer • Client manager • Patient manager • Simulators and services • Other services • GUI Integration testing/ black box testing for each module

  9. Database and persistence layer

  10. Patient manager

  11. Client manager

  12. Simulators and services

  13. Other services

  14. GUI/ display

  15. Verify that the system comply with the specified requirements. Our goal is to test the entire system after the integrations of all the modules • Define some domains and test the boundary values System testing

  16. 1. JMeter Producer Sampler • The Producer Sampler will send messages to an ActiveMQ Server. The Producer Sampler has the following parameters: • Server URL • Duration (min) • No. of Producer • Message Size (bytes) • Messaging Domain • Message Interval 2. JMeter Producer Listener Performance testing

  17. 3. JMeter Consumer Sampler The Consumer Sampler has the following parameters: • Server URL • Duration (min) • No. of Consumer • Messaging Domain 4. JMeter Consumer Listener Performance testing

  18. Comments and suggestions from team members

More Related