Hot answers tagged

12

If the product is at the MVP stage and your QA is just getting started, there's a problem. As a BA I saw this time and time again with dev vs QA where the dev team only got the BA to do testing when they felt the product was "ready to deliver to QA" which is a notion all developers should aim to dispel. Most developers went to university and took some ...


9

Are you aware that “Most of the bugs in software are due to incomplete or inaccurate functional requirements?” What would be the best use of QA engineer's time while the project is in an early stage? Test the requirements itself, not the product... by asking the right questions to uncover & challenge implicit assumptions in the requirements....


6

Although all observations are valid, from a project point of view, I am missing the motivational and learning point of view. Starting some automation now can also be part of the learning of that engineer, and the team. He will be motivated as he can do something he wants to do. Yes, the product will change. But he can also grow along with the development of ...


4

I agree that it may be too early for much automation. But there is still a lot QA can bring to the project to help it be successful at this stage. If it were me on the project, along with learning everything I could about the requirements, I would be looking at what the customer(s) really do & what their workflow is, what our competitors might offer ...


3

note: I assume you are CTO or similar role or the "boss" for QA stuff In order to clarify my "idea" of QA during project/product development, I've write down following workflow as example: requirements: formalize them, update them, take track on every release, as use case or user story. define tests: define how user story are tested, with edge cases should ...


3

It sounds like you're on the right lines already but, in addition to going through the requirements and getting familiarised with the roadmap, it's definitely worth getting him to exploratory test the MVP and get a feel of the product as early as possible. Also, static testing the requirement document would be beneficial as it allows for early feedback and ...


3

Issue fixed... solution is: params: { myVariable: function () { ... ... }, otherProperty: 'Value' } and this how you can reach in spec files: browser.params.myVariable or browser.params.otherProperty with this we can make a variable accessible from protractor.conf.js to spec test files. The following posting was helpful and ...


3

I definitely understand the want to do it through the UI. Seems so much easier. I think that you're on the right track though to start doing it with the UI. The data will be much closer to what you actually need to test. But, this should only be a start for you. Ideally, these dumps are there for good and never change. Here's a couple of ideas. In all ...


2

First of all, e2e tests tend to be brittle due to many steps that can go wrong. That's why you should limit the number of e2e tests (and UI tests in general). Always remember you want to have a test piramyd, not the test ice-cream cone. But, for those tests you are automating, RCRCRC heuristic can be useful: Of course, this works for all testing, but it ...


2

If Agile environment: I recommend you combine two things: Guidance from the Agile Test Pyramid and Agile Testing Quadrants This makes sure you have a small number of e2e tests which is hard to do Guidance form the business about what is supported, what to test, what breaks, etc. You will need to work closely with the business to turn the Pyramid and ...


2

We have a lot of this kind of report where I work. Our developers provide the following in order to test them on Dev/test servers: A webpage that allows the report update/generation task to be run. For us, this means individual buttons that trigger Cron jobs that run the reports. Another web page that allows the time to be changed for each individual ...


2

if it makes sense to write some environment-specific tests ? Absolutely! This is also frequently the job of smoke tests which basically assert that the latest deployment was successfull with very simple tests such as 'can I reach the page or do I get a 404' Testing the tests is an essential part of any quality automation system. You should generally test ...


2

I totally had the same experience as you. For a new angular project i looked into protractor as the recommended way but then just risked using java + selenium because, as you, i found that the protractor features where either not usable or have been ported to java. So far I had no problems with element locators and i don't have to wait for anything (at least ...


2

The implementation of webdriverIo is slightly different from selenium. In webdriverIO $('table').$$('td') will check for direct child 'td under 'table', and as td is not a direct child it won't return anything. instead, try: $('table').$$(' td') (See if this works) or $$('table td') Space in 'CSS' is similar to // in xpath Better raise issue with ...


2

The purpose of describe is to allow BDD format: describe('Given user logins', () => { describe('Given user Selects payment', () => { describe('Given user clicks pay', () => { it('Then deducts payment', () => { }) }) }) }) So it's perfectly fine to nest the describe. You can write steps in ...


2

I think it's a good time to ask questions about how you're defining quality for the app (ie, how quick it needs to be, how accessible it needs to be, supported browsers) I've also found that test automation can take a little time to get up and running. There's lots of drivers to be installed and/or docker/virtual machine type containers to get up and running,...


1

How is the tool Giving output ? Is it printing to console? Or a file?. You can access docker outputs by the following methods. If tool/SUT(service under test) is printing to console you can access the docker logs and get those data. docker logs -f IF output is stored to a file say ./output.txt Access that file docker cp <target_path> <...


1

Surprisingly there is no tool to support multi client scenarios and synchronization out of the box as far as I know (looking for a new startup idea ?). The general architectural problem you are trying to solve is one test, running somewhere, while controlling and getting feedback from N clients. This means you'll need the following building blocks: A ...


1

Why not just stub out the database and deal only with Entities? Databases are details which you can: (1) - Check behavior independently; (2) - Isolate your use cases from. If you want to set up a component check for a service, all you need to do is boot up the service, create the necessary Entities and perform a call to its endpoints. If you want to ...


1

No, You should NOT use static waits, it is a bad practice. Instead...Read below Disclaimer : I am an actual Protractor SDET, who has been using Protractor from last couple of years in actual Large Projects. Using Hard coded waits(static wait) along with every statement is an very bad practice for multiple reasons: It slows down the whole batch execution, ...


1

I think you can use the implicitlyWait option, although it has been removed from the Protractor documentation: onPrepare: function(){ browser.manage().timeouts().implicitlyWait(3000); }, Code example from: https://stackoverflow.com/questions/33299567/where-to-put-implicitlywait-in-protractor Read this!!!: Is it a bad practice to use implicit wait in ...


1

You can use browser.ignoreSynchronization=true entirely for angular/non-angular pages and use your own wait mechanism using ExpectedConditions to handle elements. Either way is using driver methods directly as below, so it won't wait for $http and $timeout expect(browser.driver.findElement(by.css('.msgtext')).getText().toBe('expexted text') Please let me ...


1

Config file has a params option: Based on https://github.com/angular/protractor/blob/5.4.1/lib/config.ts: "The params object will be passed directly to the Protractor instance, and can be accessed from your test as browser.params. It is an arbitrary object and can contain anything you may need in your test. This can be changed via the command line as: --...


1

Need to discuss, the concern team members Business Analyst, Developer, Testing member about the project scope. One idea will be generated how to go into for testing. Also preparing self document ( if u don't have document) . If u have read it under stand it. Try to ask as much questions as possible. Make a note of it. And start testign. Read more: https://...


1

Issue fixed. I think this posting here is really too old and just doesn't work as it should be. First of all here is the one which would run without issues, and you also find the comments which explain what each function does etc. Code in protractor.config.js added in onPrepare() method looks as following: var MailListener = require("mail-listener2"); ...


1

I would test the browser and the mobile app as if they are separate browsers. Write the requirements for one test, have it run twice, once for each environment. You could even have the two separate frameworks, one for each app, that call on the same set of test scripts.


1

In that case, have to initialize and keep two web driver objects up and running during test run.One for web browser and one for mobile app(using tools like appium). After having this structure, you may switch between different driver objects depending on test step as having few steps/assertions in web browser and few in mobile app as part of single ...


1

Have you tried simply scrolling to the bottom without any reference to any object: element(by.className('<any element on page>')).click();//to focus on page first where scroll need to happen browser.executeScript('window.scrollTo(0,document.body.scrollHeight)').then(function() { //whatever you need to check for here } );


1

Read static data from external json files to reuse across multiple tests however any dynamic data (which may change state during test runs) avoid reusing across tests as it may make your tests brittle and flaky. Sample json file: { "appURL": "http://testApp123.com", "Username": "testUser@domain.com", "Password": "testPassword", "Title":"SUT" }


1

In order to be DRY, you would need data files: This article may help setting up data files and using them across Protactor E2E Tests.


Only top voted, non community-wiki answers of a minimum length are eligible