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

Issue119 user flag tests #4

Conversation

mikebentley15
Copy link

Fixes PRUNERS#119 (finishing)

Description:
This new pull request adds automated tests for the new functionality (see the Tests section)

Documentation:
None. This is a tests-only change

Tests:
Added tests for:

  1. Test that not specifying the [[compiler]] section at all gives the default compilers with their default values
  2. Test that specifying compilers, but not specifying the optimization levels gives the default optimization levels for that compiler type
  3. Test that specifying compilers, but not specifying the switches list gives the default switches list values for that compiler type
  4. Test that the provided list of optimization levels and switches are used, and nothing more
  5. Test that by only specifying one compiler, only that specified compiler is used
  6. Test error cases in the configuration file, such as specifying more than one of a certain type of compiler

There are additional tests needed, not for this feature change, but for other functionality of the configuration file, and of flit update in general. These are outside of the scope of this change, so a new issue will be generated to round out the rest of the needed tests for this command-line subtool.

mikebentley15 and others added 24 commits November 21, 2018 17:34
Specify the minimum version of binutils
tst_nocompilers.py

flitutil: add extract_make_vars() function

This function returns ALL makefile variables as a dictionary instead
of the other extract_make_var() function that extracts only one at a
time.  This is useful for introspection and if many variables are
desired
It was intended to have what was intended in future versions
of the configuration file, but it provides little purpose now
that the issues on github are used
They weren't testing with thier actual needed configuration file,
but rather with the default configuration file, of which causes
all tests to pass anyway.
This tests error paths in handling the config file
@mikebentley15
Copy link
Author

This pull request also merges in the recent changes in the devel branch. Just look at the last 6 commits.

These automated tests that are added are the kinds of tests expected from a pull request. This particular change made quite a large change for the end-user, and thus required a lot of testing.

@mikebentley15 mikebentley15 changed the base branch from devel to feature/flags_toml December 13, 2018 01:09
@mikebentley15
Copy link
Author

If you accept this pull request, I will accept the final pull request into PRUNERS/FLiT/devel.

@mikebentley15 mikebentley15 deleted the issue119-user-flag-tests branch April 9, 2019 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants