-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make functional tests runnable via CFE_ES_START_APP_CC command #1281
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 9, 2021
Merge the "testrunner" app and put the runner logic into cfe_assert lib. Converts the "testcase" library into an app that simply calls the logic in cfe_assert to do the test. This means that the test can be run on demand by issuing the ES start app command, rather than putting it into the startup script.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 12, 2021
Merge the "testrunner" app and put the runner logic into cfe_assert lib. Converts the "testcase" library into an app that simply calls the logic in cfe_assert to do the test. This means that the test can be run on demand by issuing the ES start app command, rather than putting it into the startup script.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 12, 2021
Merge the "testrunner" app and put the runner logic into cfe_assert lib. Converts the "testcase" library into an app that simply calls the logic in cfe_assert to do the test. This means that the test can be run on demand by issuing the ES start app command, rather than putting it into the startup script.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 12, 2021
Merge the "testrunner" app and put the runner logic into cfe_assert lib. Converts the "testcase" library into an app that simply calls the logic in cfe_assert to do the test. This means that the test can be run on demand by issuing the ES start app command, rather than putting it into the startup script.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 14, 2021
Adjust the event types so that Start/End are "info" events, not debug events (in the default platform config, debug events are not shown). Also update documentation to correct the startup script entries.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 20, 2021
Use a constant at the top of the file, and change the names to match current environment.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 20, 2021
Use a constant at the top of the file, and change the names to match current environment.
astrogeco
added a commit
that referenced
this issue
Apr 22, 2021
Fix #1281, remove testrunner and convert testcase to app
zanzaben
pushed a commit
to zanzaben/cFE
that referenced
this issue
Apr 22, 2021
Merge the "testrunner" app and put the runner logic into cfe_assert lib. Converts the "testcase" library into an app that simply calls the logic in cfe_assert to do the test. This means that the test can be run on demand by issuing the ES start app command, rather than putting it into the startup script.
zanzaben
pushed a commit
to zanzaben/cFE
that referenced
this issue
Apr 22, 2021
Adjust the event types so that Start/End are "info" events, not debug events (in the default platform config, debug events are not shown). Also update documentation to correct the startup script entries.
zanzaben
pushed a commit
to zanzaben/cFE
that referenced
this issue
Apr 22, 2021
Use a constant at the top of the file, and change the names to match current environment.
zanzaben
pushed a commit
to zanzaben/cFE
that referenced
this issue
Apr 22, 2021
Fix nasa#1281, remove testrunner and convert testcase to app
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In the functional test proof-of-concept, the test cases are libraries that are loaded in the startup script, and the "testrunner" app actually runs them. But because libraries are not loadable/unloadable via command, it requires a custom startup script, and restarting CFE in order to run tests.
Describe the solution you'd like
The functional tests should be integrated with test runner such that they are each their own app, therefore runnable by simply issuing the ES command to start the app if they were not part of the initial startup script.
Additional context
This will simplify the process of running tests on targets, since it will alleviate the need to customize the startup script.
The
cfe_assert
library itself will likely need to remain as a library, because it is a common dependency between all test apps. But it shouldn't hurt to simply load this by default in the sample startup script, it won't interfere with FSW.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: