Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group Part 2: Functional Testing

June 2002REGNET Project Team Meeting Content Group 2 Functional tests are based on use cases. The goals of these tests are to verify: - to ensure proper system functionality, including navigation, data entry, processing, and retrieval Goals are not to define additional requirements (=> usability tests, task-oriented). Goals Functional Tests - An introduction Based upon black box techniques: Verifying the application and its internal processes by interacting with the application via the Graphical User Interface (GUI) and analysing the output or results Methodology Based on the Use Cases already prepared during the requirements phase

June 2002REGNET Project Team Meeting Content Group 3 UC Import / export existing data from local system Upload and conversion for different data management systems Functional Tests - An introduction Use Case => Test Case (An Example)

June 2002REGNET Project Team Meeting Content Group 4 Functional Tests - Status 72 Test cases for data generation, search & retrieval completed High level test cases for the other components (56) Test cases available

June 2002REGNET Project Team Meeting Content Group 5 Problems & Open Issues Functional Tests - Problems Problems: Test cases are all not complete: - it is not defined how the output should look like - it is not defined how the input should look like - false and right inputs are not specified (actions which occure when false input was made) Suggestion (original draft): Carry out the tests for the available test cases at first (content provider). 3 content partners, effort estimation: 2 days per partner! Report not only incidents but also further specifications, e.g. if the output is not formatted appropriately it could be defined now. ? Problem: Use cases are not very specified! Could be a possibility to detect white spots in requirement definition

June 2002REGNET Project Team Meeting Content Group 6 Validation schedule: Start on 1st of July 2002 ! Step-by-Step approach Sofia Meeting Test finalising Functional tests Usability tests (heuristic, scenarios) 06/28/0207/05/0207/19/0215/08/2002 Which functionality is available ? Content (integrity and quality) tests Red light: external solution Orange light:improvements necessary/possible before carrying out further tests Green light: go for usability tests Functional Tests - Schedule draft

June 2002REGNET Project Team Meeting Content Group 7 Strategy for pragmatic testing!? High-level testing - functionality available or not? Detailed testing could be carried out by using the test cases already worked out and/or the pure use case list !? The modelling of further test cases is very time-intensive... - Estimation: 300 test cases for all use cases quality level 5 until End of June (VALT), Modelling: 10 days, testing: 25 days - Responsiblities (CP/TP) for modelling and testing Must be carried out in the first 2 weeks of July! Functional Tests - Strategy

June 2002REGNET Project Team Meeting Content Group 8 Functional Tests - Discussion - Reponsible content partners - Test cases for the other functionalities vs. pragmatic approach - Agreement on reporting workflow Working groups: Practical exercises ? After Sofia: Creation of test manual, Carrying out tests, Reporting and monitoring, Functional tests QA To be done in this session/working groups Reporting Workflow E-Shop/Catalogue Management Auction System E-Publishing Topic Map (Generator), Viewer? Data Generation Search (Multi-Site search?) Portal (Heuristic Evaluation)

June 2002REGNET Project Team Meeting Content Group 9 - To define communication worflows during (also after ?!) the validation phase - To enable tracking of all incidents - To enable tracking of tests carried out - To enable priorisation of work to be done - To enable the consortium to define dates for the release of the system Functional Tests - Incident Reporting and Change Management Why? Decision already made: no automatic tool

June 2002REGNET Project Team Meeting Content Group 10 Tester Tests with test cases Submit one report per incident to tech-partner Validation PM Adds incident to open incidents list Keeps track of reported incidents Keeps track of timelines Tech Partner Receives incidents Functional Tests - Incident Reporting

June 2002REGNET Project Team Meeting Content Group 11 Tester Receives reports on resolved incidents Validation PM Sets status of incidents in open incidents list to resolved Tech Partner Resolves incidents Reports resolved incidents to tester and Validation PM Functional Tests - Incident Solving

June 2002REGNET Project Team Meeting Content Group 12 Tester Tests resolved incidents with test cases Submits reports on resolved incidents to Validation PM Validation PM Sets status of incidents to closed Functional Tests - Closing Incidents

June 2002REGNET Project Team Meeting Content Group 13 Tester Tests with test cases Re-opens incidents (if necessary) Validation PM Sets status of incident to re-opened Keeps track of reported incidents Keeps track of timelines Tech Partner Receives re-opened incident reports for resolving Functional Tests - Re-opening Incidents

June 2002REGNET Project Team Meeting Content Group 14 Validation PM Sends weekly status reports on incidents to Technical Partners and all Testers Reminds Technical Partners on all important pending issues Reminds Testers on all outstanding tests to be carried out Functional Tests - Weekly Reporting

June 2002REGNET Project Team Meeting Content Group 15 The next page is for developers comments Reporting Form

June 2002REGNET Project Team Meeting Content Group 16 Reporting Log