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

Comprehensive rewrite of Char tests #158

Merged
merged 1 commit into from Feb 4, 2015

Conversation

Projects
None yet
2 participants
@jonathanhefner
Contributor

jonathanhefner commented Feb 3, 2015

Like #150, I rewrote the Char tests to be more comprehensive. All exposed API functions are covered and tested with all alpha-decimal characters. The tests are also more structured, so it is easier to add tests for future corner cases (e.g. toLocaleLower in a Turkish locale).

@jonathanhefner

This comment has been minimized.

Show comment
Hide comment
@jonathanhefner

jonathanhefner Feb 3, 2015

Contributor

I'm... not sure what happened to the build. Travis CI says the build timed out, but the tests run swiftly (and pass) locally. Is it possibly a glitch in the build system? Is there a way to trigger another attempt?

Contributor

jonathanhefner commented Feb 3, 2015

I'm... not sure what happened to the build. Travis CI says the build timed out, but the tests run swiftly (and pass) locally. Is it possibly a glitch in the build system? Is there a way to trigger another attempt?

@jonathanhefner

This comment has been minimized.

Show comment
Hide comment
@jonathanhefner

jonathanhefner Feb 3, 2015

Contributor

Looks like it was just a glitch.

In case anyone is curious, I was able to force another build by doing an empty git commit --amend and then a git push -f to my branch.

Contributor

jonathanhefner commented Feb 3, 2015

Looks like it was just a glitch.

In case anyone is curious, I was able to force another build by doing an empty git commit --amend and then a git push -f to my branch.

@evancz

This comment has been minimized.

Show comment
Hide comment
@evancz

evancz Feb 3, 2015

Member

Why do you put single tokens in parentheses?

Member

evancz commented Feb 3, 2015

Why do you put single tokens in parentheses?

@jonathanhefner

This comment has been minimized.

Show comment
Hide comment
@jonathanhefner

jonathanhefner Feb 3, 2015

Contributor

Just for consistency. I guess it also feels a little easier to eyeball with the parens acting as delimiters, but that's subjective.

If it's bad practice (or just ugly), I can strip them out.

Contributor

jonathanhefner commented Feb 3, 2015

Just for consistency. I guess it also feels a little easier to eyeball with the parens acting as delimiters, but that's subjective.

If it's bad practice (or just ugly), I can strip them out.

evancz pushed a commit that referenced this pull request Feb 4, 2015

@evancz evancz merged commit 4825a2a into elm:master Feb 4, 2015

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details
@evancz

This comment has been minimized.

Show comment
Hide comment
@evancz

evancz Feb 4, 2015

Member

I'd generally consider it bad style to have extra parens, but I only care to the extent that people will use these tests as a guide for writing their own. I'm not sure what the right thing is here, but it feels weird.

In any case, things look good, thanks!

Member

evancz commented Feb 4, 2015

I'd generally consider it bad style to have extra parens, but I only care to the extent that people will use these tests as a guide for writing their own. I'm not sure what the right thing is here, but it feels weird.

In any case, things look good, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment