-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Protractor tests #1063
Comments
I think its related #547 |
👍 to including protractor examples, I'd love to see this. |
I would like to interact with the button on the dialog component. However protractor can't select the button e.g. Any ideas? |
@JJB1980 Are you missing the |
I'd love to see an example of such a test as well. I've been trying (and failing) to write some Protractor tests in a project I'm working on that makes use of Angular Material. |
+1 Beside e2e tests, a lot of code is not being unit tested, example: https://github.com/angular/material/blob/v0.9.0-rc2/src/components/gridList/gridList.spec.js And even with the presence of unit tests for a component, new commits don't come with tests, example: 6c7734e |
While e2e tests will be provided in the future, they are not currently a priority; our current focus is component implementation, unit tests, performance, and effects. |
+1 |
It seems there is no e2e tests with Protractor in this project for the moment.
It would be useful to have an example of test for each component. There is some component like "Toast" that does not seem easy to test since DOM Elements can appear for only few seconds.
It could also be nice to have some "Locator" specific to material design components.
For example, the input field in the "Text Field" component is wrapped by md-input-group.
The following:
is transformed in something like this
But in my test I want to be able to get the input element, and not the md-input-group. And as a user of the library I don't want to know how it is implemented because implementation can change.
So it would be very helpful to have a locators like this:
The text was updated successfully, but these errors were encountered: