Repository navigation
Syntactic sugar for instantiating Components in tests #615
Description
describe('MyComponent', () => {
it('should instantiate', @Injectable (tb:Testbed) => {
var element:Element = tb
.directive(MyDirective, { override: [new Template(...), new Component(...)] })
.compile({
html: '<my-component a="b" [c]="exp">lightdom</my-component>')
.instantiate({some instance or Type})
.element;
});
});
});
@Component({
selector: 'my-component'
})
class MyComponent{}
Metadata
Metadata
Assignees
Labels
No labels
Activity
vicb commentedon Feb 16, 2015
Some remarks:
Traceur does not support types for arrow functions:
(tb:Testbed) => nulldoes not compile,function(tb:Testbed) { return null;}is oksee google/traceur-compiler#1580
Reflexion information are not added to anonymous functions:
If you have
it(name, function(tb:Testbed) {...})then you can not retrieve the reflexion info on the anonymous functionsee google/traceur-compiler#1760
vsavkin commentedon Feb 24, 2015
Since testing is an important part of the Angular story, it'd be great to see a design of the test infrastructure before we start implementing it.
For example, how do we support the following use cases:
Some of them do not have a good answer in AngularDart. In Angular2, where everything is hierarchical, they will be even harder to solve.
mhevery commentedon Feb 24, 2015
I can take a stab at creating a design doc/ issues
mhevery commentedon Mar 25, 2015
https://docs.google.com/document/d/1qFfHwYCOLpLuTap_l6TCEaU4I0C-pVFVbTl2o4-XbUo/edit
vicb commentedon Apr 6, 2015
closed via #1160
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.