Skip to content

Software QA Plan & Report

AmeliaWen edited this page Oct 27, 2020 · 17 revisions

Quality Assurance methods: The main concept of having a software quality assurance plan is to be able to define appropriate coverage criteria of the testing functionalities from the business methods, RESTful service and integration test. Moreover, the software quality assurance plan documents the static testing of our code, namely code review.

These are the 2 main testing approaches for software assurance testing.

  • Static V&V -- analyses of the code
  • Dynamic V&V -- exacting the code

Dynamic testing

For deliverable 2, we tested our business methods in Service classes through JUnit testing, then we tested our RESTful service located in controller classes through AdvanceRestClient. In the meanwhile, integration is tested through Travis CI through out the development process of deliverable 2.

Unit Testing of Backend This is the first main step in our QA plan. To test the functionality of the service classes, we tested individually for each service class and independently of real database through Mockito Framework. We set our goal for test coverage to 90 % due to the time constraints. The tables below showed the average of desired and achieved test coverage for all service classes

Testing coverage |Testing Average | Desired coverage | Achieved coverage | |-----| -----| |Business methods in service classes | 90% | |