This presentation was done by Charles Poisson, Apps, Web and Cloud Services Qualification Manager at Aldebaran Robotics, during the NAO sur Seine User-Group in Paris on october 21st It gives some insights on how Aldebaran Robotics is testing applications at the moment, and on what can developers do to get their app ready for it.

1. Cliquez pour modifier le style des
sous-titres du masque
Qualification Applications
Charles Poisson – 22/10/2013
Monitoring - Charles Poisson
1

2. Some definition
“Validation activities aim at confirming that a
product meets its customer’s expectations”
So…?
The objectives of the application qualification team
are to protect robots and guarantee a minimal
level of quality for application delivered on the
store.
Monitoring - Charles Poisson
2

3. Publication - TESTS
STORE
DEV
TESTS
Publication for Validation
Feed back (OK – NOK)
If the application meet our
check lists the application is
APPROVED for public release
DevProg Apps Validation - Charles Poisson
3

4. Check list (short extract)
Shake List ?
PACKAGING
• Title of application is ok and nao can say it
• Manifest is ok (trigger words ok, no bad words)
• English is available
• Description is synthetic and easy to understand
• Application image does not infringe copyright
• Application image is good looking
• A video present the application
Robot and Human Safety
• The robot does not harm itself
• The robot does not fall (frequently)
• The robot does not ask user to do
something dangerous
• Shall not modify system image…
Monitoring - Charles Poisson
Apps Execution
• No obvious flaws or bugs
• Apps is responsive
• Respect Ethics codes
• The application can be exited in a
standard way.
4

5. Some advices on testings
test! test!
• Basic tests
 Verify the qualification check list
 Check logs for errors or warnings.
test!
test!
• Functional tests
 It’s better to write your own functional test!
• Performance tests
 Check the heating of the robots joints when using the application.
• Reliability tests
 Do not hesitate to test your behaviors at the mechatronics limits of
the robot (Joints hot, repeat moves many times)
 Check for instabilities or loss of balance!
 Long run of your application to see if it fails after a while.
Monitoring - Charles Poisson
5

6. Q&A
Thanks for listening.
Questions?
Monitoring - Charles Poisson
6