Skip to content

Releases: ist181045/es1617-adventures

ADVENTURE_5

29 May 01:08
Compare
Choose a tag to compare

Implemented JMeter load test cases. Unfortunately, due to time and availability constraints, a report containing the test cases' analysis about the FenixFramework's optimistic transaction policy or the environment the tests were run wasn't written.

ADVENTURE_4

29 May 01:08
Compare
Choose a tag to compare

Fourth delivery

Interfaces for every module created:

  • Activity

    • #104: Create interface with Activity Provider form + list of providers
    • #105: Create interface with Activity form + list of activities
    • #106: Create interface with Activity Offer form + list of offers per activity
    • #107: Create interface with list of reservations per offer
  • Bank

    • #100: Create interface with Bank form + list of banks
    • #101: Create interface with Client form + list of bank's clients and operations
    • #102: Create interface with Account form + list of accounts per client
    • #103: Create interface for withdrawal and deposit operations
  • Hotel

    • #97: Create interface with Hotel form + list of hotels
    • #98: Create interface with Room form + list of rooms
    • #99: Create interface with Booking form + list of bookings per room

ADVENTURE_3

29 May 01:08
Compare
Choose a tag to compare

Third Delivery

Activity, Bank and Hotel modules' domain is persistent and said persistence is tested through persistence tests (see XPersistenceTest, where X is the name of the module).

Unfortunately, with almost no time to spare, we noticed BulkRoomBooking still wasn't persistent.. Meaning we missed it.. We still tried to rectify it, but not in time for this delivery, unfortunately. So, not due to lack of knowledge per se, but we were misguided.

Admittedly, we were induced erroneously, since it was said, during a class, that the broker module was fully implemented. A direct quote from the teacher himself. Taking it to heart, the word was spread and we didn't bother to profusely check the module, only checking the dml and that the tests would run in a global context (the broker module wasn't compiling either, even after installing the required dependencies).

ADVENTURE_2

29 May 01:07
Compare
Choose a tag to compare

Second Delivery

A broad showcase of test results and code coverage report follows:

Test Results

  • Activity: 69 out of 69 tests ✔️
  • Bank: 49 out of 49 tests ✔️
  • Broker: 97 out of 98 tests ❌
    • Failures:
      • UndoStateProcessMethodTest#CancellRoomActivityPaymentException()
  • Hotel: 68 out of 68 tests ✔️

Overall Coverage Summary

Package names were shortened for readability and formatting purposes.

📦 Package Class, % Method, % Line, %
📦 All Classes 97.4% (38/39) 93.4% (256/274) 91.1% (830/911)
📦 p.u.t.s.activity.dataobjects 100% (1/1) 100% (15/15) 100% (23/23)
📦 p.u.t.s.activity.domain 100% (4/4) 97.7% (42/43) 84.3% (129/153)
📦 p.u.t.s.activity.exception 100% (1/1) 50% (1/2) 50% (2/4)
📦 p.u.t.s.bank.dataobjects 100% (1/1) 100% (11/11) 100% (16/16)
📦 p.u.t.s.bank.domain 100% (6/6) 100% (41/41) 97.8% (131/134)
📦 p.u.t.s.bank.exception 100% (1/1) 50% (1/2) 50% (2/4)
📦 p.u.t.s.broker (Application) 0% (0/1) 0% (0/2) 0% (0/10)
📦 p.u.t.s.broker.domain 100% (12/12) 97.7% (85/87) 93.4% (326/349)
📦 p.u.t.s.broker.exception 100% (2/2) 50% (2/4) 50% (4/8)
📦 p.u.t.s.broker.interfaces 100% (3/3) 53.8% (7/13) 53.8% (7/13)
📦 p.u.t.s.hotel.dataobjects 100% (1/1) 89.5% (17/19) 92.9% (26/28)
📦 p.u.t.s.hotel.domain 100% (5/5) 100% (33/33) 98.2% (162/165)
📦 p.u.t.s.hotel.exception 100% (1/1) 50% (1/2) 50% (2/4)

ADVENTURE_1

29 May 01:07
Compare
Choose a tag to compare

First Delivery

A total of 138 test cases have been implemented, all of which pass!

  • Activity: 38 test cases ✔️
  • Bank: 34 test cases ✔️
  • Broker: 25 test cases ✔️
  • Hotel: 41 test cases ✔️

Albeit coverage might not be at a full 100%.. We might've missed something