Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group 2002-06-24 - 2002-06-26...
-
Upload
mackenzie-burke -
Category
Documents
-
view
214 -
download
0
Transcript of Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group 2002-06-24 - 2002-06-26...
Cultural Heritage in REGional NETworksCultural Heritage in REGional NETworks
REGNETREGNET
Project Meeting Content Group
2002-06-24 - 2002-06-26
Part 2: Functional Testing
June 2002 REGNET 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 introductionFunctional Tests - An introduction
Based upon black box techniques:
Verifying the application and itsinternal processes by interacting
with the application via theGraphical User Interface (GUI) and analysing the output or results
Methodology
Based on the “Use Cases” alreadyprepared during the requirements
phase
June 2002 REGNET Project Team Meeting Content Group
3
UC 1.1.3 - Import / export existing data from local systemUpload and conversion for different data management systems
Test Case 1.1.3 - Import / export existing data from local system
Action Data Input Expected Output
Expected Results
OK
or reported
as Bug No.
Rechecked
Import data Click on„Import data“
Request to determine (= place, type, format,name) data
Determine data,Describe data inprovided Fill in-Form OR field/s
Dataset 1,Click on „ok“
Systems lists data to be imported, request toconfirm, modify or cancel procedure
Confirm import Click on„confirm“
System confirms import of data
Functional Tests - An introductionFunctional Tests - An introduction
Use Case => Test Case (An Example)
June 2002 REGNET Project Team Meeting Content Group
4Functional Tests - StatusFunctional Tests - Status
72 Test cases for data generation, search & retrieval completed
High level test cases for the other components (56)
Test cases available
June 2002 REGNET Project Team Meeting Content Group
5
Problems & Open Issues
Functional Tests - Problems 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 notspecified (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 alsofurther 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 detectwhite spots in requirementdefinition
June 2002 REGNET 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/02 07/05/02 07/19/02 15/08/2002
Which functionality is available ?
Content (integrity and quality) tests
Red light: external solutionOrange light: improvements necessary/possible before
carrying out further testsGreen light: go for usability tests
Functional Tests - Schedule draftFunctional Tests - Schedule draft
June 2002 REGNET 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 Functional Tests - Strategy
June 2002 REGNET Project Team Meeting Content Group
8Functional Tests - Discussion 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
ReportingWorkflow
E-Shop/Catalogue ManagementAuction SystemE-PublishingTopic Map (Generator), Viewer?Data GenerationSearch (Multi-Site search?)Portal (Heuristic Evaluation)
June 2002 REGNET 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 Functional Tests - Incident Reporting and Change Managementand Change Management
Why?
Decision alreadymade: no automatictool
June 2002 REGNET Project Team Meeting Content Group
10
Tester
Incident Reports
Validation PM Technical Partner
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 ReportingFunctional Tests - Incident Reporting
June 2002 REGNET Project Team Meeting Content Group
11
Reports onResolved Incidents
Validation PM
TechnicalPartner
Tester
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 SolvingFunctional Tests - Incident Solving
June 2002 REGNET 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”
Reports Incidentsto be closed
Validation PM
Tester
Functional Tests - Closing IncidentsFunctional Tests - Closing Incidents
June 2002 REGNET Project Team Meeting Content Group
13
Technical Partner
Re-openedIncident Reports
Validation PM
Tester
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 IncidentsFunctional Tests - Re-opening Incidents
June 2002 REGNET Project Team Meeting Content Group
14
Validation PM
Technical Partner Tester
W eekly Reporton Open Incidents
Tester
Tester
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 ReportingFunctional Tests - Weekly Reporting
June 2002 REGNET Project Team Meeting Content Group
15
The next page is for developers comments
Reporting FormReporting Form
June 2002 REGNET Project Team Meeting Content Group
16
Reporting LogReporting Log