21.04.2013 Views

ETTC'2003 - SEE

ETTC'2003 - SEE

ETTC'2003 - SEE

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6. Automatic validation<br />

Principles<br />

Automatic validation principles are the following [Lloret, Dasia 2002] :<br />

• The automatic validation technique enables to execute test-cases without operator and perform<br />

specified TM verifications. Presently, this technique makes use of Satellite Digital Simulator<br />

SINUS, taking benefit of functions such as pause and simulation time acceleration.<br />

• Automatic validation is based on translator p2s which converts FCPS (pil syntax) into SINUS<br />

scripts (tcl syntax).<br />

• Executing such a script consists in sending TC and verifying TM parameter values.<br />

• Test scripts provide test-cases implementation. A test script instruction can be : (1) context<br />

restoration; (2) FCP execution; (3) programming message execution.<br />

• A test log-book is automatically produced for a posteriori analysis.<br />

Operational Procedures<br />

(Control Plan)<br />

Translator<br />

Objectives<br />

Operational<br />

Procedures<br />

(SINUS)<br />

Procedure call<br />

TC<br />

TM effects<br />

to check<br />

Test script<br />

Test monitoring<br />

SINUS<br />

(accelerated time)<br />

6<br />

Test<br />

log-book<br />

Global objectives of automatic validation are the following :<br />

1. Improve testing reliability :<br />

• With automation, operator errors are not longer possible (send a wrong TC or forget to check<br />

TM effects).<br />

• Procedures are respected strictly. TM effects are verified exhaustively which is very difficult<br />

when performed manually because TM effects may be many and because of real time<br />

constraints. Also observation delays between TC and their TM effects can be traced more<br />

precisely.<br />

• Produced test log-books are necessarily complete opposed to log-books written manually: Every<br />

sent TC is traced together with TM verification results. Simulation configuration is traced in the<br />

test log-book : on-board central SW release, simulator release and initial context, the version of<br />

each sent TC. Furthermore, test log-book formalisation enables automatic comparisons when<br />

performing non-regression tests.<br />

2. Improve testing efficiency :

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!