Sample of definitions of “Done” (Project B)

Done (items completed in each sprint)

Automated testing

  • Class unit testing (JUnit)
    • Execution of all test cases must be successful.
      • The following classes are within the scope of Selenide automation.
        • Controller
      • The following classes are not included in automatic testing as they are settings files.
        • Config
    • Coverage (C1 branch coverage) must be confirmed.
      • Coverage must be confirmed in the development environment. (IDE)
      • Coverage must be confirmed in both a self-check prior to the review and the review itself.
        • Coverage should generally be 100% for the following classes.
          • Form/Bean (coverage does not need to be obtained for getter and setter.)
          • Service
          • Util (coverage does not need to be obtained for elements involved in PDF output as this is confirmed in a visual inspection.)
          • Custom validators (coverage only needs to be confirmed within isValid methods.)
        • Coverage does not need to be measured for the following classes as they are covered in tests of the class from the reference source.
          • Dto
          • Dao
          • Entity
          • Constants
  • UI testing (Selenide)
    • Execution of all test cases must be successful.
    • The authentication and authorization function must operate correctly.
    • The following browsers are supported.
      • Front Office System (Chrome)
      • Back Office System (Chrome)
    • The details of the test must be indicated in TestCases. (TestCases operation procedure)
  • The following perspectives must be covered in automated testing.
    Test Type & Viewpoint Catalog

Other automated testing

  • Manual testing
    • The screen layout in the following browsers must be confirmed.
      • Front Office System (Chrome)
      • Back Office System(IE11)
    • Operation in the Front Office System screens must be confirmed using an emulator.
      • iPhone 5S (to confirm that no areas are cut off when using the model with the smallest screen size.)
      • Android 7.0 (Nexus5) (because Android7 has the largest market share (33.54%) as of February 21, 2018.)
    • Front Office System screen operations must be confirmed on actual devices. (any model can be used as variance between devices will be confirmed in variation testing.)
      • iPhone7
      • Android8.0(XPERIA SOV36)
    • The details of the test must be indicated in TestCases. (TestCases operation procedure)
    • The following perspectives must be covered in manual testing.
      Test Type & Viewpoint Catalog
  • The content output to PDFs must be confirmed. (Selenide results are confirmed visually.)
  • No errors with a high severity left in static analysis.(Checkstyle/FindBugs).
  • DML for operation (review) of the developed features must be created and confirmed.
    Storage location: https://www.XXXXdev01.com/gitlab/

Undone (items that are not completed in each sprint)

  • Testing that is not included in automated testing.
    • Usability testing
    • Performance testing
      • Performance testing
      • Stress testing
      • Long-run testing
      • Volume testing
    • Security testing
    • User acceptance testing
    • Variation testing for smartphones
  • Creation of design documents
    • Release plan
    • Interface design documents
    • Service and function list
    • Screen transition map
    • External design documents
    • Basic specifications
    • Code definition rules and master data
    • Service overview and operation flowchart
    • Library version management policy
    • Test policy
  • Open an account
  • Risk checking of new products
  • Web application diagnostics
  • Requests to appear in app stores
    • Distribution to actual devices
  • Internal meeting for release judgment