I could see a shadow DOM in your webpage and in that case you have to use .shadow()(Cypress Docs). Your code would look something like: cy.get('view-login').shadow().find('input[data-field="username"]').type('username', {force: true}) cy.get('view-login').shadow().find('input[data-field="password"]').type('password', {force: true}) cy.get('view-login').shadow().find('input[value="personal"]').click() cy.get('view-login').shadow().find('.ViewLogin__button').click()

There is no comma , at the end of video URL in your videos list. videos = [ "https://www.youtube.com/watch?v=COAdbTDTDFc", "https://www.youtube.com/watch?v=p_2wemVUQnc", "https://www.youtube.com/watch?v=A8fODOFiBq0", "https://www.youtube.com/watch?v=tmgT01e1sGQ", "https://www.youtube.com/watch?v=_eqEuBp3jJw", "https://www.youtube.com/watch?v=09IRNL2TsHM", "https://www.youtube.com/watch?v=uUIugt-GsbY", "https://www.youtube.com/watch?v=HqlBwWX218s", "https://www.youtube.com/watch?v=DrKafd3U4TY" ]

Agree. Faced same condition before. As experienced earlier few things might help you at some extend. You need to convey them the pros & cons of the automation testing. You need to give them a brief about the use of automation as well. I mean with lesser knowledge one can expect to much from you. You need to take initiatives to keep balance between actual possible things to automate and expectations As per my knowledge, In your case of browser automation we can ensure that everything is working well 24*7. This is a primary goal of browser automation. Communicate clearly if we are not bothering about things should work ALWAYS then we should think of reduce the dependency & efforts on browser automation Limitations: Its really out of scope [as of now at lease] to automate browser to catch images or content overlapping, veriication of image quality and visibility, crosschecking on different versions of browser in [responsive] website

Hope you are using appium server with Appium application. Solution: Open Appium.exe Go to settings and click on it. Select "Over ride existing sessions" and click on it. Bingo you are done.

The methods .isDisplayed() and .isEnabled() have nothing in common. Method .isDisplayed() : An element is considered displayed when it is perceptually visible to the human eye. https://www.w3.org/TR/webdriver/#element-displayedness Method .isEnabled() : An element is considered enabled if it's not a form control (button, input, textarea, select or option) or when the user interactions and focus are not blocked with the disabled attribute/property. https://www.w3.org/TR/webdriver/#is-element-enabled For the default implementation: https://github.com/SeleniumHQ/selenium/blob/master/javascript/atoms/dom.js

Since mobile development is agile, this needs to use test automation. Mobile development can be agile. It is not a given. Test automation can be done in any paradigm. Do emulators work 100% accurate? I can't say 100% but they are getting more accurate (I haven't had an issue since iOS 6). For Android, make sure to use an AVD with Google Play API services. I have experience in Selenium webdriver/grid and c# scripting Then you'll be at home writing Appium/Java tests. To me, C# and Java are basically the same. Especially when using common libraries like Selenium. Alternatively, I use Xamarin to test iOS and Android with great success. I am not sure about how cross-device/platform work in mobile testing. I keep my desktop browser and mobile tests separate. They are different products and behave differently. I also keep my iOS and Android test projects separate. Any tips on mobile testing and automation in general? Testing on mobile isn't different. As an example: an input is still an input and can be tested the same. One thing to remember is that automated testing on mobile is like Selenium/browsers in that it just controls the app (or browser) and not the OS. It can be a chore to do things outside the app like disable wifi or handle system alerts.

The error message cy.type() can only accept a string or number. You passed in: undefined says the last part of the path is undefined, e.g this.data.fullName or this.info.userGoodCredit.company. If this.data was undefined, you error would be cannot get property "fullName" of undefined, so your beforeEach() is probably ok. It looks like there's a typo in the property used in the test, or in the fixture object. Check with console.log(this.info.userGoodCredit) and console.log(this.data).

I think the condition attribute is missing: - task: PublishTestResults@2 inputs: failTaskOnFailedTests: false testRunner: VSTest testResultsFiles: '**/*.trx' searchFolder: '$(Build.Repository.LocalPath)' condition: succeededOrFailed() From the documentation: In this YAML, PublishTestResults@2 will run even if the previous step fails because of the succeededOrFailed()

I would say that is the lowest possible severity, but that might vary depending on the rules of your team or some specifics about the app. For example, a factor that might make that a high severity bug is when font colors are part of a brand or something like national flag colors or similar where changing colors might significantly change the user perception of the app. Another example is accessibility and readability. Some colors might not work with other colors on the page so changing them might alter usability of the app for certain categories of users.

You would have to load all your data into objects from the fixtures, but you could then add each response to an array and shift each time inside a while loop. Your error reporting won’t be great but you should be able to process all of your data sets with minimal code duplication. Something like this, maybe: it(‘tests my data sets’, () => { const datasets = [dataset1, dataset2, dataset3]; while(dataset.length > 0) { cy.intercept('GET', '/todos', req => req.reply(datasets.shift())); cy.get(‘items’).should(‘be.visible’); } });