-
Notifications
You must be signed in to change notification settings - Fork 531
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
Create unit tests for new fields #40
Comments
I'm going to try after I read a bit more about Karma |
OK, but firstly I have to solve the external lib loading problem. |
I added external libs to karma. So now can be improve new fields unit tests. 776f6c4 |
(I was about to suggest that 😄 )
From the doc |
Oooo.... what?!?! |
basically, don't do this:
but this:
|
You can use arrows because we use webpack as preprocessor and webpack use babel |
Unit test are going through Webpack ? Wow ok, I didn't know... Webpack does everything 😲 |
Sorry, I missed that totally |
Nop, so you can use any ES6 feature |
Sweet! |
what field test are you make? Because I plan to make an other field tests |
I'm starting with #36 |
What we need to test in this external fields:
|
I make |
I'm going to try |
Ok, for multiselect I recommend you to use |
Roger that ! :) Le 23 août 2016 16:46, "Icebob" [email protected] a écrit :
|
It was too early for #44, I made several mistakes that I'm fixing |
My bad sorry about that |
Nop :) |
fieldMasked done. |
fieldPikaday, fieldSlider done. |
fieldSpectrum done. |
fieldGoogleAddress "done" |
Wow cool, you are on 🔥 |
Now I start the last fieldCleave too. |
All test done. 🎉 I made some changes, so if you open the karma debug page ( http://localhost:9877/debug.html ) for test debugging, you will see a similar page instead of empty white blank page 😄 |
That's so cool ! I need your help with the doc:
I hope we can finish everything early next week. |
Merged #51 |
The text was updated successfully, but these errors were encountered: