I am new to Golang. And I am looking for automating signup, login processes in a web app. Please suggest a good tool like Selenium and how can I implement it in the go language.
I want to do the following process automatically using Golang:
Start a browser. Currently, I'm using https://github.com/skratchdot/open-golang
Auto entry on the signup page and auto-submit a form.
Login check for the registered user. Everything needs to be done automatically for more users.
You can also use Playwright for Go, which is a wrapper for the Playwright project. Playwright provides a single API to automate Chromium, Firefox, and WebKit to automate browsers which was created by Microsoft. With it you interact with the sites, record videos, make screenshots, and emulate other browser specific behaviour.
If you are going to use GO for web automation testing - Selenium is a good option. Still it's nothing more than a library that allows you to interact with browsers. So you are going to need to develop your own framework or reuse someone already implemented.
My advice is to consider Agouti, since it supports Ginkgo BDD and xUnit Gomega. Everything else is pretty much the same from architectural perspective. You can design it like any other language binding. There are common patterns that appear over and over again in browser automation frameworks, like
PageObjects: A simple abstraction of the UI of your web app.
LoadableComponent: Modeling PageObjects as components.
BotStyleTests: command-based approach
Another good resource for building your Test framework is the xunitpatterns guide. It gives a great content overview of the patterns, smells and refactoring strategies you can use. Also look at this test frameworks tutorial. It'll help you choose the most proper solution for your case.
My guess is that you are going to need some CI server support for
everything needs to be done auto for more users.
Here is a good article how-to achieve this with TravisCI.
update:
you can use Selenium for Golang
Related
I am using rest-assured dependency in my project for testing API's with selenium.
Can anyone guide me why basically we use rest-assured dependency in API testing ? (Tried finding the answer from my seniors who developed our project framework and online, i couldnt get any answer why are we using this, it would help me if anyone guides me with the reason ?)
And what are the other ways to do API automation using selenium ?
why should we use them ? (in comparison with rest-assured ?)
Thank you.
Selenium is not typically used for REST API testing. Selenium is a tool that can control web browser. Despite a web browser is a sort of HTTP client, it is very specific client that is intended for browsing web and maintain high level of user security. The above puts certain degree of restriction of what you can and cannot do with the browser. For example:
You can only fire GET request from the address bar
You can do POST request using HTML form but you have to have an HTML page with the form and fixed set of parameters
You can overcome the above if have the page with any javascript client so that you can configure different requests configurations
Points 2 and 3 basically mean you have another level of communication in your framework and that level has to be properly maintained. That's because Web Browser is not naturally intended for interacting with API. But only with very narrow part of what HTTP can offer (again we can overcome that restriction by javascript code executed within the browser but that would be another level of complexity).
RestAssured is pure HTTP client with some handy and neat functionality allowing to easily manipulate with requests and responses. So it allows to fire any type of requests supported by HTTP protocol, parse responses responses and verify them (often all in a single statement).
The latter is naturally designed for interacting with REST API, does not introduce extra levels to your tests, does not have limitation like the browsers have.
Recap
The below schema demonstrates the difference of having your API tests implemented in both approaches:
Selenium case:
Selenium binding lib -> Web Driver -> Browser -> API GET (rarely others - need to maintain special file for that)
Rest-Assured case:
Rest-Assured lib -> API ANY SORT OF REQUESTS
P.S. - In the same way as RestAssured handles API case much effectively than Selenium, Selenium handles Web Testing in much more effective way than RestAssured since the latter cannot neither control browsers nor even execute JAvaScript code. That is why we have two such a powerful and great tools each of which perfectly serves the needs it naturally designed for.
Just because Rest-Assured (RA) is a code-based tool to test API. It supports:
make HTTP(s) request
extract value from response
assert response
Selenium is tool to control web browser, it CANNOT do API testing.
I don't know why you compare Selenium to Rest-Assured. They are 2 different tools that serves 2 different purposes.
Is there an easy way to test some web page looking for some errors. I mean usually while doing web testing we want to check the display which could be very difficult to maintain.
So I wanted to know if as an alternative strategy there are some practice to massively test the URLs of a website and just look for any kind of error including JS error in the console.
I think it is possible using a framework like Selenium but it might be a bit overkill no ?
Also the idea will be to do that on a production server, in addition to test server.
The website have some authentication so just hitting the URLs will not work.
I am struggling to test Angular JS application, Can someone provide me reference to learn that, Couldnt find any.
I want to attack the application but it seems not all links are being visited by Crawler.
How are you exploring the application?
In ZAP you should use the Ajax Spider as this will launch browsers in order to explore it. The standard spider will not be as effective.
I had to recently updgrade from jQuery 1.3 to 1.10. As a result lots jquery code was changed and plugins were upgraded. And consequently this resulted in lot of hours of manual testing.
This got to me think that there should be a better way of testing/validating pages after any js/css change across my site.
I would like to do the following.
crawl all pages on my site.
Check all links on page work correctly
Check for basic html tag validation
Check for any JS & css errors.
jquery version compatible code
Any recommendations for tools that will allow me to perform all of the above test.
Thanks
Free tools exist for quite many of those tasks. There are both web page based validators and browser plugins. I don't know if some tool would do all the below in one or couple steps, but these should get you at least started.
For crawling the site and checking all links you can use tool from The World Wide Web Consortium (W3C):
http://validator.w3.org/checklink
The results page also provides links for for validating html and css of each page.
If you want to validate a file otherwise, you can straight use
http://validator.w3.org/
and
http://www.css-validator.org/
For validating javascript syntax, you can use jslint
Finally, if you want to be more sure that your javascript is working correctly, write unit tests for example with QUnit
Is there a way to test logging into a site with open id using Selenium?
In Selenium all the tests live in the server, so once filled the open id URL in the appropriate field in the web page I am taken to the 3rd party web page for entering the credentials and my test can't run anymore.
Is there a way around this?
Yes - use Selenium RC. It gets around the cross-domain problem of basic Selenium Core and allows you to script against multiple sites.
I guess, technically speaking, you could include a really dumb OpenID server on your testing domain, but Patrick's suggestion of a testing framework that supports cross-domain operations sounds like a much better idea.
Although, I guess that depends on what you're trying to test. It could be that using a third party OpenID server is bad for your tests, because a change to the UI of that server could cause your tests to break. Or maybe you want to make sure that your code is interoperating correctly with that server, in which case using the 3rd party is exactly what you want to test.