Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

entry_point() in script creates a limbo for untested code #436

Open
schwancr opened this issue Sep 8, 2014 · 0 comments
Open

entry_point() in script creates a limbo for untested code #436

schwancr opened this issue Sep 8, 2014 · 0 comments

Comments

@schwancr
Copy link
Contributor

schwancr commented Sep 8, 2014

Our scripting system has a bunch of code in the entry_point(), that isn't currently tested by test_wrappers, which will only run the <script>.main(*args) function.

This can mean that bugs slip through if the code in that section is not trivial. There are two alternatives I suppose:

  1. Rework all of the scripts so that entry_point only contains the code for parsing the command-line args
  2. Add an additional test for each script, which uses os.system to call the script from the command line.
@schwancr schwancr changed the title entry_point() in script creates a limbo for untested code entry_point() in script creates a limbo for untested code Sep 8, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant