Non regression testing for the JOREK code

Ahmed Ratnani (IRFM); Chantal Passeron (IRFM); Eric Nardon (IRFM); Francois Orain (IRFM); G. Huysmans; Guilhem Dif-Pradalier (IRFM); Guillaume Latu (IRFM; INRIA Nancy - Grand Est / IECN / LSIIT / IRMA); LaBRI); Marina Becoulet (IRFM)

arxiv: 1211.3823 · v1 · pith:WXEHTGCJnew · submitted 2012-11-16 · 💻 cs.DC · math.AP

Non regression testing for the JOREK code

Guillaume Latu (IRFM , INRIA Nancy - Grand Est / IECN / LSIIT / IRMA) , Marina Becoulet (IRFM) , Guilhem Dif-Pradalier (IRFM) , Virginie Grandgirard (IRFM) , Matthias Hoelzl (IPP Garching) , G. Huysmans , Xavier Lacoste (INRIA Bordeaux - Sud-Ouest)

show 6 more authors

Eric Nardon (IRFM) Francois Orain (IRFM) Chantal Passeron (IRFM) Pierre Ramet (INRIA Bordeaux - Sud-Ouest LaBRI) Ahmed Ratnani (IRFM)

This is my paper

classification 💻 cs.DC math.AP

keywords coderegressionaimsbehaviourjorektestingapplicationautomation

0 comments

read the original abstract

Non Regression Testing (NRT) aims to check if software modifications result in undesired behaviour. Suppose the behaviour of the application previously known, this kind of test makes it possible to identify an eventual regression, a bug. Improving and tuning a parallel code can be a time-consuming and difficult task, especially whenever people from different scientific fields interact closely. The JOREK code aims at investing Magnetohydrodynamic (MHD) instabilities in a Tokamak plasma. This paper describes the NRT procedure that has been tuned for this simulation code. Automation of the NRT is one keypoint to keeping the code healthy in a source code repository.

This paper has not been read by Pith yet.

Non regression testing for the JOREK code

discussion (0)