Failing unit tests on macOS with German localization
See original GitHub issueCurrent behavior
<Please describe here what faulty behavior you are experiencing> On macOS with German localization the unit tests fail.Expected behavior
<Please describe here the expected behavior> The unit tests should succeed.Steps to reproduce the problem
- clone autoNumeric and run
yarn && yarn test
FAILED TESTS:
The AutoNumeric object
initialization methods
✖ should correctly initialize the AutoNumeric element when the `formatOnPageLoad` option is set
Firefox 61.0.0 (Mac OS X 10.13.0)
Expected '12234678.321' to equal '$12,234,678.32'.
<Jasmine>
./test/unit/autoNumeric.spec.js/</</<@webpack://autonumeric/test/unit/autoNumeric.spec.js:1150:12 <- tests.webpack.js:9:705409
<Jasmine>
Initialization calls
Initialize a single AutoNumeric object
✖ should fail to init when the default value is outside of the min and max limits
PhantomJS 2.1.1 (Mac OS X 0.0.0)
TypeError: undefined is not an object (evaluating 'aNInput.remove') in tests.webpack.js (line 9)
webpack://autonumeric/webpack/universalModuleDefinition:1:0 <- tests.webpack.js:9:1481375
<Jasmine>
autoNumeric options and `options.*` methods
`options.*` methods
✖ should correctly update the `decimalPlacesShownOnFocus` option
Firefox 61.0.0 (Mac OS X 10.13.0)
Expected '2.222,12 €' to equal '2.222,1235 €'.
<Jasmine>
./test/unit/autoNumeric.spec.js/</</<@webpack://autonumeric/test/unit/autoNumeric.spec.js:1483:12 <- tests.webpack.js:9:734042
<Jasmine>
Instantiated autoNumeric functions
`selectInteger`
✖ should select only the decimal part
Firefox 61.0.0 (Mac OS X 10.13.0)
Expected '12.266,123 €' to equal '12.266,123457 €'.
<Jasmine>
./test/unit/autoNumeric.spec.js/</</<@webpack://autonumeric/test/unit/autoNumeric.spec.js:5157:12 <- tests.webpack.js:9:990807
<Jasmine>
The AutoNumeric event lifecycle
✖ should send the 'autoNumeric:formatted' event when formatting is done
Firefox 61.0.0 (Mac OS X 10.13.0)
Expected spy formattedEvent to have been called 6 times. It was called 5 times.
<Jasmine>
./test/unit/autoNumeric.spec.js/</<@webpack://autonumeric/test/unit/autoNumeric.spec.js:8420:8 <- tests.webpack.js:9:1305434
<Jasmine>
I’ll try to investigate this further.
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
Testing Your Internationalized App
Explains how to create a user interface and write code that can be localized into multiple languages.
Read more >Localization Unit Test
The unit test should fail and show us that ALERT_VIEW_TITLE is missing a localization in both English and German. The unit test itself...
Read more >Xcode 4, breakpoints not working in unit tests for Mac OS ...
I have a simple Mac OS X Command Line Tool project in Xcode 4.5. I manually added a unit test target off of...
Read more >Spring Boot unit-test fails when building master due to ...
Spring Boot unit-test fails when building master due to translation of a message with not expected locale #6106.
Read more >Unit Testing on macOS: Part 1/2 - RayWenderlich.com
In Xcode go to the File Navigator and select the High RollerTests group. Select File\New\File… and choose macOS\Unit Test Case Class. Click Next ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DanielRuf my bad, I created the
Marked for deletion
label, but in reality it should readmarked for closing
, or something like this. I never ever deleted an issue; as you mention, it’s pretty irresponsible to delete issues from an issue tracker (except perhaps in the case of credentials being pasted)!Edit: There, I modified the label to
Inactivity detected
, and I’ll update the auto-reply tooHey Daniel, were the bugs still happening when running the tests automatically/manually?