This wiki is obsolete, see the NorduGrid web pages for up to date information.
Testing/ARC-InfoSys emi1 rc1
Test report
EMI_Test_Report_ARC-Infosys_EMI1_RC1.pdf
Component Description
- Savannah task: https://savannah.cern.ch/task/?18670
- Modules and Components: ARIS, EGIIS, ARC Grid Monitor
The ARC Infosys components are responsible for storing and presenting of informations collected on CE or SE. They include the "Local", LDAP-based information system (ARIS, ARC Resource Information System) and the LDAP-based Index service, the EGIIS. As a special "client", the grid monitor provides visualization of the information content of both the ARIS and EGIIS services.
Code analysis
- Tester: Marek
- due: for every RC
- Sloccount:
cpp: 136167 (74.26%) perl: 18590 (10.14%) php: 13007 (7.09%) python: 10545 (5.75%) sh: 4199 (2.29%) ansic: 798 (0.44%) java: 63 (0.03%)
Total Physical Source Lines of Code (SLOC) = 183,369
The complete results of SLOC count entire ARC code can be found here
______________________________________________________________________
- CCCC metrics:
| Metric | Tag | Overall | Per Module | |
|---|---|---|---|---|
| Number of modules | NOM | 890 | ||
| Lines of Code | LOC | 106028 | 119.133 | |
| McCabe's Cyclomatic Number | MVG | 30720 | 34.517 | |
| Lines of Comment | COM | 12674 | 14.240 | |
| LOC/COM | L_C | 8.366 | ||
| MVG/COM | M_C | 2.424 | ||
| Information Flow measure ( inclusive ) | IF4 | 618184 | 694.589 | |
| Information Flow measure ( visible ) | IF4v | 618047 | 694.435 | |
| Information Flow measure ( concrete ) | IF4c | 3341 | 3.754 | |
| Lines of Code rejected by parser | REJ | 3197 |
The complete results for CCCC for entire ARC code can be found here
Later the results will be split between components.
Unit tests
- Tester: Anders
- due for every RC
Results of unit test code coverage for entire ARC code can be found here:
http://hep.nbi.dk/~waananen/nordugrid/20781/
The text description of results will come later.
Later the results will be split between components.
Regression tests
- Tester: Marek
- due for every RC
initially the verification of resolved bugs
R1
Deployment tests
D1: clean installation
- Tester: Marek
- due: for every RC
D2: upgrade installation
- Tester: Marek
- due: postponed
Functionality tests
F1: ARIS
- Tester: Marek
- due: 1 April
Testing how the resource information generated by the information providers are periodically updated in the ARIS.
F2: EGIIS
- Tester: Marek
- due: 1st April
Testing registrations, de-registrations.
F3: Grid Monitor
- Marek
- due 25 March
some basic tests, that the grid monitor bla bla...
Performance tests
P1: ARIS service reliability
- Tester: Adrian
due: due 25 March
Services run by the component must maintain a good performance and reliability over long periods of time with normal operation. Long running unattended operation test measuring performance of the product. Service must not show performance degradation during a 3-day period.
P2: EGIIS service reliability
- Tester: Mattias
- due: 25 March
Services run by the component must maintain a good performance and reliability over long periods of time with normal operation. Long running unattended operation test measuring performance of the product. Service must not show performance degradation during a 3-day period.
P3: ARIS load test
- Tester: Florido
- due 1st April
Check if ARIS can handle 100 hundreds concurrent client query
P3: EGIIS load test
- Tester: Mattias
- due 25 April
Check if EGIIS can handle 100 hundred concurrent client query
Scalability tests
S1: ARIS
- Adrian
- due May
Check how ARIS behaves with increasing number of job entries on the cluster.
Standard compliance/conformance tests
- see the glue2 tests in ARC-CE tbd: put link
Inter-component tests
- check later interoperability with glite site and top BDII
