Skip to content
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

Move one emulator and IOC test to a support directory #6555

Closed
DominicOram opened this issue Jun 3, 2021 · 3 comments
Closed

Move one emulator and IOC test to a support directory #6555

DominicOram opened this issue Jun 3, 2021 · 3 comments
Assignees
Labels
5 no_release_notes Tickets that do not need release notes, use sparingly!

Comments

@DominicOram
Copy link
Contributor

DominicOram commented Jun 3, 2021

As a support person I would like to be able to specify in the IOC test framework where my emulator and test are. Currently they're in a central location but as of #6131 we want to move them around. I would then like to put the emulator and tests into the support directory and be able to run "make ioctests" from this directory to run the test.

Acceptance Criteria

  • The emulator and test paths can be specified when running the IOC test framework
  • A simple IOC has the tests and emulator moved into it's support directory (preserving history)
  • Running "make ioctests" in this directory runs the IOC Test
  • Running "make ioctests" in EPICS_TOP recursively runs all tests (including this one), this is done as part of the IOC system tests jenkins build and the results are correctly uploaded to jenkins
  • It is documented on Move emulator and IOC tests into support module #6556 how to do this exactly for other IOCs (remember to preserve history)
  • The wiki is changed to match this new structure
  • The ioc generator script is corrected to match this Pulled into IOC generator: issues #4659
@rerpha
Copy link
Contributor

rerpha commented Jun 18, 2021

we should document that as a developer we should still run the command from support\ioctestframework\master as it is more verbose and you can more easily pass options to the command such as -f or -tm DEVSIM etc.

on the build server or just running for sanity you could use make ioctests

@aaron-long
Copy link
Member

Can you add the ability for the IoCTestFramework run_tests.py and the drivers associated tests to be called via a bat file in the driver directory. As discussed this improves the developer workflow for being able to see a line-by-line output of test results. We are a happy for now that the make ioctests does not give results until finished if this is an alternative option.

@DominicOram
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 no_release_notes Tickets that do not need release notes, use sparingly!
Projects
None yet
Development

No branches or pull requests

5 participants