Changes between Version 5 and Version 6 of Testing and Validation


Ignore:
Timestamp:
05/18/26 23:08:35 (8 days ago)
Author:
193284
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Testing and Validation

    v5 v6  
    66
    77The tests validate booking conflict prevention, RSVP consistency validation, and availability checking functionality implemented during the advanced database development phase.
     8
     9The overlap validation tests explicitly cover:
     10* partial overlap at the beginning
     11* partial overlap at the end
     12* complete overlap
     13* fully contained intervals
     14* non-overlapping intervals before existing bookings
     15* non-overlapping intervals after existing bookings
    816
    917== 1. Venue Booking Conflict Test ==
    … …  
    3543=== Expected Result ===
    3644
    37 The trigger prevents overlapping venue bookings for the same date and time interval.
    38 
    39 == 2. RSVP Validation Test ==
     45Creates the initial booking interval used for overlap testing.
     46
     47== 2. Venue Overlap Validation Cases ==
     48
     49=== SQL Code ===
     50
     51{{{
     52#!sql
     53-- Overlap case 1
     54SELECT is_venue_available(
     55    1,
     56    '2026-06-20',
     57    '19:00',
     58    '23:00'
     59);
     60
     61-- Overlap case 2
     62SELECT is_venue_available(
     63    1,
     64    '2026-06-20',
     65    '16:00',
     66    '19:00'
     67);
     68
     69-- Overlap case 3
     70SELECT is_venue_available(
     71    1,
     72    '2026-06-20',
     73    '17:00',
     74    '23:00'
     75);
     76
     77-- Overlap case 4
     78SELECT is_venue_available(
     79    1,
     80    '2026-06-20',
     81    '19:00',
     82    '21:00'
     83);
     84
     85-- Non-overlap case 1
     86SELECT is_venue_available(
     87    1,
     88    '2026-06-20',
     89    '14:00',
     90    '17:00'
     91);
     92
     93-- Non-overlap case 2
     94SELECT is_venue_available(
     95    1,
     96    '2026-06-20',
     97    '22:00',
     98    '23:00'
     99);
     100}}}
     101
     102=== Expected Result ===
     103
     104The first four cases return FALSE because the intervals overlap with the existing booking.
     105
     106The last two cases return TRUE because the intervals do not overlap.
     107
     108== 3. RSVP Validation Test ==
    40109
    41110=== SQL Code ===
    … …  
    63132Guests who declined RSVP cannot be marked as attending.
    64133
    65 == 3. Venue Availability Function Test ==
    66 
    67 === SQL Code ===
    68 
    69 {{{
    70 #!sql
    71 SELECT is_venue_available(
    72     1,
    73     '2026-06-20',
    74     '18:00',
    75     '22:00'
    76 );
    77 }}}
    78 
    79 === Expected Result ===
    80 
    81 Returns FALSE if the venue already has a conflicting booking.
    82 
    83134== 4. Photographer Availability Function Test ==
    84135
    … …  
    212263The testing scenarios confirm that the implemented trigger functions, SQL functions, views, and constraints operate correctly and enforce the required business rules inside the PostgreSQL database layer.
    213264
    214 The validation process demonstrates successful conflict prevention, integrity enforcement, and analytical reporting functionality for the Wedding Planner Management System.
     265The validation process demonstrates successful overlap prevention, integrity enforcement, analytical reporting, and advanced interval validation functionality for the Wedding Planner Management System.