How to run "tests" and "examples" should be added

[lcarasik]

It is a common feature to test every new install and run tests during code development to ensure the code still functions as intended after modifications are made. It would be useful to add this how to run tests and run examples to the documentation as part of the quick start page.

[emerzari]

Lane, every new commit is tested through Travis. Paul was here referring to a case that is part of NekExamples and not part of the test suite that is run at every commit. That Benard case should be run as part of the overnight tests on Jenkins (not on every commit because it takes too long to run all the examples every time). This was the case at least until a while ago. We will look into this. On Dec 30, 2020, at 11:35 AM, Lane Carasik <notifications@github.com<mailto:notifications@github.com>> wrote: It is a common feature to test every new install and run tests during code development to ensure the code still functions as intended after modifications are made. It would be useful to add this to the documentation as part of the quick start page. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#112>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AELXDLDN5WXC5OCEOPWLNODSXNJGZANCNFSM4VOPZMXQ>.