Skip to content

Conversation

@hanneskaeufler
Copy link
Contributor

Reference to a related issue in the repository

None - These are out of context quality of life improvements in the automated test suite

Add a description

I saw some long-hanging fruit in improving these tests. I hope the commit messages do
well enough to explain the change/intention behind it. If not, feel free to comment on details :)

Check the checklist

  • My code and comments follow the style guidelines and contributors guidelines of this project.
  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests / travis ci pass locally with my changes.

When forgetting to install the protobuf compiler,
an error message is shown which had a missing
space between two words.
@jdsika jdsika requested a review from vkresch December 9, 2019 16:33
@jdsika jdsika added the Quality Quality improvements. label Dec 9, 2019
@jdsika jdsika added this to the v3.1.3 milestone Dec 9, 2019
@jdsika
Copy link
Contributor

jdsika commented Dec 9, 2019

Thank you Hannes for your contribution. It is very welcome! @vkresch will review it tomorrow

Copy link
Contributor

@vkresch vkresch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the improvement! Looks nice and pythonic :). Just change one line for the newline warning and we can merge it.

Copy link
Contributor

@vkresch vkresch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@vkresch
Copy link
Contributor

vkresch commented Dec 12, 2019

@jdsika there seems to be an issue with the status report form travis to merge this PR see here for more how to maybe solve it https://travis-ci.community/t/known-issue-travis-ci-reports-expected-waiting-for-status-to-be-reported-on-the-github-status-api-but-the-status-never-arrives/1154

@jdsika
Copy link
Contributor

jdsika commented Dec 12, 2019

I do not find the option. Very strange...

@jdsika
Copy link
Contributor

jdsika commented Dec 13, 2019

@hanneskaeufler I invited you to the organization. Maybe this is the problem of the status not being properly reported. Can you accept the invite and make an empty commit (not reopen of PR) as a member? If this does not work @vkresch will copy your stuff and make a branch.

There is no reason to traverse the file
line by line if all we care about is the
last character.

This also uses unittests subTest to show
the file which fails the test.
When one file is failing, due to the
fact that all tests contain for loops,
the other failures are swallowed because python
stops running the test on the first assertion.
With subTest one can introduce a subcontext which
allows showing all of the failed files as well a
diagnostic as to which file failed.
Python provides mechanisms for that, no
reason to manually track a count.
The globs where repeated a whole bunch of times
which is both information duplication as well
as unneccessary work.
There is no reason to guard the assertions
in the conditional.
@hanneskaeufler
Copy link
Contributor Author

@hanneskaeufler I invited you to the organization. Maybe this is the problem of the status not being properly reported. Can you accept the invite and make an empty commit (not reopen of PR) as a member? If this does not work @vkresch will copy your stuff and make a branch.

Thanks! I accepted and rebased one more time ...

@hanneskaeufler hanneskaeufler mentioned this pull request Dec 13, 2019
6 tasks
@jdsika jdsika removed this from the v3.2.0 milestone Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Quality Quality improvements.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants