This wiki is obsolete, see the NorduGrid web pages for up to date information.

Testing/ARC-Core emi1 rc1

From NorduGrid
Jump to navigationJump to search

Test report

EMI_Test_Report_ARC-Core_EMI1_RC1.pdf

Component Description

ARC-Core is represented by components responsible for hosting web services, allowing the set up of different security layers and higher-levels of information transfer. Apart from the HED, ARC Core module also contains all the common, shared utilities of ARC software. On these components we will try to test the usage of different MCCs and security layers (using the echo service). Additionally we will use the perftest utility to test the stability of the components.

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

NO 'CRITICAL' OR 'BLOCKER' BUGS RELATED TO THESE COMPONENTS SINCE LAST STABLE RELEASE (1.2.1)

Deployment tests

D1: clean installation

  • Tester: Marek
  • due for every RC

D2: upgrade installation

  • Tester: Marek
  • due: postponed

Functionality tests

F1: ARCHED daemon

  • Zsombor
  • 1 April
  • Deployment of an echo service using arched container and different MCC types
  • Test of authentication, responses and stability of deployed service using arcecho command

F2: arched command line options

  • Tester: Jon
  • due: 25 March

Test the command line options of arched, if they work according to documentation.

  • -h, --help Show help options
  • -f, --foreground run daemon in foreground
  • -c, --xml-config=path full path of XML config file
  • -i, --ini-config=path full path of InI config file
  • -d, --config-dump dump generated XML config
  • -p, --pid-file=path full path of pid file
  • -u, --user=user user name
  • -g, --group=group group name
  • -s, --schema=path full path of XML schema file
  • -v, --version print version information

Performance tests

WILL NOT BE DONE FOR RC1

P1: service reliability

  • Tester: Gabor
  • 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. First time see the times to return 100 arcecho requests (simultaneous and sequential). Then repeat a following cycle for three days - every 5 minutes use the perftest utility with input parameters 50 threads, 30 seconds. After every day try to measure the times to return 100 arcecho requests (simultaneous and sequential) and make some conclusion when comparing the times to times from beginning of test.

Package: EMI1-RC1

  • at the beginning
    • arcecho request time
Sequential:
real    0m10.240s
user    0m0.935s
sys    0m0.431s
Simultaneous:
real    0m1.663s
user    0m0.867s
sys    0m0.423s
    • Memory usage:
%CPU %MEM    VSZ   RSS
 0.3  0.6 202864  6436


  • after one day
    • arcecho request time
Sequential:
real	0m10.275s
user	0m0.985s
sys	0m0.505s

Simultaneous:
real	0m1.912s
user	0m0.900s
sys	0m0.504s
    • Memory usage:
%CPU %MEM    VSZ   RSS
 2.9  4.8 471312 49848


  • after two days
    • arcecho request time
Sequential:

Simultaneous:
    • Memory usage:
%CPU %MEM    VSZ   RSS
  • at the end
    • arcecho request time
Sequential:

Simultaneous:
    • Memory usage:
%CPU %MEM    VSZ   RSS


  • conclusions
    • by VERBOSE log level: disk space need for a log arround 100MB/ 15 minutes

Scalability tests

S1: ws-layer response

  • Tester: Zsombor
  • due: 15 April

Testing of stability and thoughtput of deployed echo service using perftest utility

Standard compliance/conformance tests

after EMI-1 the WS-layer should be tested against standard WS toolkits.

Inter-component tests

no plans for EMI-1

Retrieved from "https://wiki.nbi.ku.dk/w/index.php?title=Testing/ARC-Core_emi1_rc1&oldid=3691"