-
Notifications
You must be signed in to change notification settings - Fork 3k
Commit
- Loading branch information
There are no files selected for viewing
7 comments
on commit 764b914
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@caitp Yeah, that's my plan. I need to figure out how to automate running the test suite against multiple versions of Angular, which I haven't had the time to research yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ProLoser @PascalPrecht Hey guys, any advice or guidance on setting up Karma to run tests against multiple versions of Angular?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nateabele --- I'll see how difficult it is to write a Karma plugin which will install different versions of bower components before running a suite --- If a plugin like that exists, then it should be trivial to just have multiple configs (as in Angular core) to run variations on the test suites
...
We may need to write this as a really ugly grunt task for now, and that kind of sucks... The plugin is writeable, but the problem is that I don't think I can really get around the asynchronous nature of the bower API to make it work, and I can't find any way to make karma plugins play nicely with async plugins. I've opened an issue about it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I guess the quickest thing to do would be to just check different versions of angular + angular-animate into the tree, and run the tests with different versions of them similar to AngularJS's jqlite vs jquery tests.
It kind of sucks having to check them into the tree, but I'm not sure how long it will be before asynchronous plugins are a thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK 1.1.X
releases were never production ready, so I personally don't see any reason in supporting outdated development versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is true @g00fy-, they were never marked as stable. However the 1.2 animation code is not in master yet, and people are apparently using the unstable stuff.
Specifying a hard deadline for the removal of the 1.1.5 stuff is probably adequate, but I think it would still be good to make sure this stuff works well with 1.0.8 for a while, even without ngAnimate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@g00fy- Some people may use ui-route
without using ngAnimate
module at all.
should probably retag this release... apparently people (or at least one person on IRC) is running into this bug, and it basically breaks any app that isn't including $animator. Kind of a bummer.
Maybe a regression test is in order here, too