Functional Testing call - Nov 29
From GEANT2-JRA1 Wiki
Contents |
[edit]
Dial in Info
This call will take place via skype. The participants in the list below will be called on skype conferencing. If you are interested in joining the call, please inform loukik or nicolas
Time: 1100 hrs UTC
[edit]
Participant List
Testing Team: Ilias, Michalis
Release Mgmt: Loukik, Nicolas
Development Team: Verena, Stijn, Guilherme, Jochen Reinwand, Stephan Kraft
[edit]
Agenda
- Status update from testing team
- Ilias
- RRD MA Installation (29/11)
- RRD MA Messages (29/11)
- Creator and deliverer scripts status (29/11)
- Michalis
- Addition of Ant targets (27/11)
- Ilias
- Future work
- Stijn
- BWCTL MP testing (18/12 - 24/1/07)
- Verena
- SSH Telnet MP testing (18/12 - 24/1/07)
- Guilherme
- Command-line MP Testing - dev. support discussion
- Loukik
- Functional specs and interface specs template work update
- Ilias
- All scripts for RRD MA ready (7/12)
- Michalis
- Improvement of output messages (1/12?)
- Discuss future work on SQL MA - Utilisation and Lightpath status metrics
- Stijn
- Next call
[edit]
Minutes
- Status update
- Ilias
- Installation of RRD MA - done
- Creator scripts - ready by end of 30/11
- Example messages - got messages from Roman..discovered 1 more
- Michalis
- Ant targets added, comments to code added
- Ilias
- Future work
- Stijn will work on BWCTL MP testing. Verena will work on CLIMP testing along with some help from RNP. Guilherme will work on SSh/Telnet MP testing. All agree that the proposed deadlines for finishing functional testing can be met. ACTION: LK, NS and GF to talk to Leobino about who else from RNP can help Verena in doing some testing
- Loukik will try to provide template drafts for review by the testing team. Release team agreed to provide feedback in 2 days time.
- Ilias mentioned that 7/12 as a deadline for finishing all scripts for RRD MA testing is still possible but a bit tight.
- Michalis aims to complete work on Output messages by 5/12. After that he will start work on SQL MA testing. He will then be able to predict how much effort would be needed. JRA4 guys will be requested to join in as well. The priority is to test lightpath status data fetching from SQL MA: ACTION: Michalis to contact Roman next week for some input on testing, Loukik to inform Roman and Szymon about this work. ACTION: LK to contact JRA4 guys to see if they can help
- Other business
- Functional Testing Code framework - The page on the wiki (http://wiki.perfsonar.net/jra1-wiki/index.php/Functional_tests) explains the framework being used for test scripts. Michalis and Ilias agreed put their code on svn. ACTION: Michalis and Ilias to email their code asap and try to put the code on svn.
- RRD MA and LS communication testing - It was agreed that the bare minimum testing that should be done for communications originating from RRD MA and going to LS would be to visually check if the messages sent by the RRD MA are appearing in the LS. For the person testing the RRD MA, the importance is on testing the features of registration/de-registration/etc whether they function properly and as documented. These visual tests should be repeated a few times. It would be ideal if there are scripts written which could do these tests. ACTION: Ilias to provide estimates as to how long would it take to write up such scripts.
- Testing underlying tools - It was agreed that the perfSONAR team is responsible for testing the features documented for the software written by the perfSONAR development team. The effort needed to test the underlying tools such as BWCTL, etc can be huge. Before using such tools as major components of the perfSONAR service, the development team is responsible for doing some tests to ensure that the tools are stable, don't have any security bugs etc. It was also agreed to take up this topic on a wider forum.
