Make selection using cypress in Angular if you're using material forms
Clash Royale CLAN TAG#URR8PPP
Make selection using cypress in Angular if you're using material forms
I have a form that looks something like this:
<form class="col s12" materialize [formGroup]="newUserForm">
...
<div class="row">
<div class="input-field col m4 s12">
<select formControlName="genderBound" materialize="material_select" id="gender" name="test">
<option value="" disabled selected name="chooseGender">Choose gender</option>
<option *ngFor="let gender of genders">gender</option>
</select>
<label for="gender">Gender</label>
</div>
...
When I try to use cypress to select the dropdown menu, it tells me that it's not visible. When I follow the explanatory URL that cypress provides, it suggest that I use force: true
inside my click. This allowed my test to pass, but never actually seemed to select the items.
force: true
I also followed the solutions provided here, and implemented a jQuery click on the actual option (Note that my select and option tags are not md-select and md-option tags)
sample.spec.js in my cypress directory:
...
it('signs up a new user', () =>{
cy.get('button[id=new-account-button]').click();
cy.get('input[id=affiliation]').type(affiliation);
cy.get('input[id=password]').type(pass);
cy.get('input[id=userName]').type(name);
cy.get('input[id=email]').type(email);
//Now the options
cy.get('[name="chooseGender"]').click(force: true);
cy.get('option').contains("Female").then(option =>
cy.wrap(option).contains("Female");
option[0].click();
);
...
I suppose there's two things I don't quite understand:
I provide a repo with my exact issue below:
git clone https://github.com/Atticus29/dataJitsu.git
cd dataJitsu
git checkout cypress-SO
Make an api-keys.ts file in /src/app and populate it with the text to follow
npm install
ng serve
(In a separate terminal tab)
npm run e2e
api-keys.ts:
export var masterFirebaseConfig =
apiKey: "AIzaSyCaYbzcG2lcWg9InMZdb10pL_3d1LBqE1A",
authDomain: "dataJitsu.firebaseapp.com",
databaseURL: "https://datajitsu.firebaseio.com",
storageBucket: "",
messagingSenderId: "495992924984"
;
export var masterStripeConfig =
publicApiTestKey: "pk_test_NKyjLSwnMosdX0mIgQaRRHbS",
secretApiTestKey: "sk_test_6YWZDNhzfMq3UWZwdvcaOwSa",
publicApiKey: "",
secretApiKey: ""
;
npm install
[############......] | extract: sill pacote rxjs@https://registry.npmjs.org/rxjs/-/rxjs-6.2.1.tgz extracted in 112447ms
When you're targeting the element for clicking that Cypress thinks isn't clickable, are you targeting the same element that highlights when you right click -> inspect element in Chrome?
– Joshua Wade
Aug 6 at 13:57
@JoshuaWade I'm not at my computer to address the first question, but regarding the second question, when I use the element inspector, it highlights elements that aren't in my html file (and hence can't assign names or ids). That's part of the issue in the first place.
– Atticus29
Aug 6 at 20:49
@JoshuaWade, I just tried the npm install from a fresh clone of the repo. Seems to work for me. Have you updated npm recently? What version are you working with?
– Atticus29
Aug 6 at 22:30
Alright, thanks - nginx is up and running! Just FYI, it looks like you accidentally removed a couple of commands when you added the API stuff. After putting in the
api-keys.ts
file, I ran npm install --save-dev
and then npx ng serve
, and then I ran npm run e2e
to start Cypress. I had to specify the integration folder as "e2e"
in the cypress.json
. However, I have run into another error at this point. When running app.e2e-spec.ts
, Cypress gives back a parse error on the first import: `ParseError: 'import' and 'export' may appear only with 'sourceType: module'``– Joshua Wade
Aug 8 at 14:34
api-keys.ts
npm install --save-dev
npx ng serve
npm run e2e
"e2e"
cypress.json
app.e2e-spec.ts
1 Answer
1
I found the following test to work with your repository (Latest commit 353633c),
describe('Test Gender Select', () =>
before(function ()
cy.visit('http://localhost:4200/')
)
it('signs up a new user', () =>
cy.get('button').contains('Create New Account').click();
cy.get('#gender').select('Female',
force: true
);
cy.get('#gender').contains('Female')
);
);
You can see from the Cypress test runner that it has indeed selected the Female option, so I believe it covers the aim of your original test.
If I try to use click()
like so
click()
cy.get('#gender').click(
force: true
);
cypress gives the message
CypressError: cy.click() cannot be called on a element. Use cy.select() command instead to change the value.
So, following this instruction and using
cy.get('#gender').select('Female');
gives the following error message about visibility, which seems to be standard for a select
using material design (both angular-material and materialize).
select
CypressError: Timed out retrying: cy.select() failed because this element is not visible ... Fix this problem, or use force: true to disable error checking.
so using force: true
option on cy.select()
fixes this problem.
force: true
cy.select()
I understand the visibility issue occurs because material design covers the parent with the options list, and Cypress uses criteria for visibility based on the parent (see this question), although now the force option works (with Cypress v3.0.3).
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
I appreciate you providing a working example! However, the
npm install
command failed for me. It's been hanging for the past few minutes at this line:[############......] | extract: sill pacote rxjs@https://registry.npmjs.org/rxjs/-/rxjs-6.2.1.tgz extracted in 112447ms
– Joshua Wade
Aug 6 at 13:55