Tag Info

New answers tagged

1

As always, it depends. If the application developers have been building unit and integration automation that runs with each build, you aren't as far behind as you would be if no low-level automated checks existed. QA is usually in charge of automated GUI checks and may also be in charge of some of the high-level headless automated checks (such as API ...


1

Usually developers write unit tests (because unit tests are close to the code developers know well). Automated GUI test use different instrumentation (Selenium?) so need a bit different skillset. Sometimes might be even developed in different language: because GUI tests are inherently slower, it might make sense to use language like Python which allows you ...


3

When is a good time to develop new automated test, and who should be responsible for this? Developing the structure of the automation can begin very early on in the process. Once the requirements are set the objects can start getting built out, be put into classes and a lot of the assertions can be built that way all that remains is ToDos that hook ...


0

GUI features are dependant on underlying DB, Services, Business logic. Before the gui is stabilized you can focus on automating services, db layer. This would help you focus on sub-systems. Also, when you need to do End to End tests, example- GUI - Service - DB level tests it would help reuse those validations. I would recommend GUI automation when the ...



Top 50 recent answers are included