Tag Info

New answers tagged

0

According to me test automation is in itself a project - test automation as far as I believe is writing a program that will be used to test another program. So how about you consult the other stakeholders or say the developers in your company. If there is a project where developers have changed over time, discuss it with them about their experience of the ...


0

In terms of straight documentation, I have found Confluence to be widely used. If documents are more informal and provide system usage guidelines, wikis, a shared server drive, or a tool like Dropbox work well with teams. Dropbox may be quick to setup, but file version issues come at a cost to this. On the other side, documentation can integrate with tools, ...


0

I've written some of these frameworks in the past and have followed a few guidelines in writing the code, and in creating design documents. My basic view is that if I have left and in 6 months someone needs to work on this, would they (or I) have the information they need to continue to work with the tool? If the answer is no, then you need to document. ...


0

If the code is for Selenium WebDriver, the documentation process can be greatly simplified with automated tools. Selenium supports Java very well, so unless you are using another language like C#, javadoc could be the way to go from a development maintenance point of view.


0

Often Selenium tests tend to become a bit messy, mainly as naturally they are initially written in a quick manner, just to progress through the scenario and as a proof of concept. In addition, extensive usage of XPATH can make the test look even more cryptic than it is already. As a result, the scripts become very hard to understand, at least from the first ...


1

Yes, definitely, documenting your project is absolutely necessary. But I'm not talking about for automation tests specifically, but for all programs in general. Selenium automation tests are programs just like anything else, which means that all coding standards within your company should also apply. The quality of the automation tests should be as high as ...


4

Yes, Selenium is an active project (see commit history on GitHub). Then why are there so many unresolved open issues? It's open source. We can't expect the team members to fix bugs on a daily basis, because they are just enthusiasts and all have real-life jobs. The developer in charge of a particular area may not have time to deal with it right away, even ...



Top 50 recent answers are included