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

Improve configuration framework for ET #61

Open
irublev opened this issue Dec 16, 2017 · 0 comments
Open

Improve configuration framework for ET #61

irublev opened this issue Dec 16, 2017 · 0 comments
Assignees

Comments

@irublev
Copy link
Contributor

irublev commented Dec 16, 2017

  1. transform the script s_install to the function install
  2. parameterize install function with confName
  3. parameterize ellipsoidsinit with confName
  4. make install pass confName to ellipsoidsinit
  5. parameterize elltool.conf.Properties.init with confName
  6. make ellipsoidsinit pass confName to elltool.conf.Properties.init
    
7) add tbxConfName parameter to the test xml configuration
 (it is necessary to descend special configuration manager for test toolbox configuration within elltool.test package)
  7. teach install accept both test and toolbox configurations
    
If the test configuraiton is specified --- install extracts tbxConfName, otherwise -
-- use the conf name directly.


  8. make run_matlab_tests_jenkins.bat pass



install(%confName%), cd .., %matlabFunc%('%runMarker%','%confName%')



into run_matlab_tests.bat instead of just



%matlabFunc%('%runMarker%','%confName%')



and remove install(%confName%), cd ... from run_matlab_cmd.bat.



Also, create run_matlab_cmd_with_conf.bat parameterized with a conf name as a wrapper around run_matlab_cmd.bat.



Then make all run bat scripts from ./install folder use run_matlab_cmd_with_conf.bat instead of 

run_matlab_cmd.bat.

  1. modify runTestPack from mlunitext.RemoteTestRunner so that it executes some special methods at its start and end, descend special class elltool.test.RemoteTestRunner that executes elltool.conf.Properties.init with current test configuration before and after performing of each test pack. This is necessary to guarantee that all the possible changes of Properties within tests are cleared so that all test packs can be executed independently.
@irublev irublev self-assigned this Dec 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant