Web UI Testing with Go
The author shares their transition from Playwright to Go for web UI testing in the Inkmi project. Go's HTTP client and goquery improved test speed and reliability, prioritizing server-rendered HTML projects' needs.
Read original article
The article discusses the author's experience with web UI testing using Go for their startup project, Inkmi. Initially using Playwright for browser tests, the author faced challenges with slow test setup and flakiness, leading to the decision to switch to Go for end-to-end testing. By directly testing web functionality with Go's HTTP client and goquery for parsing, the author achieved faster, deterministic tests that integrated well with the server-side business logic. While this approach sacrifices browser simulation and cross-browser testing, it offers speed, reliability, and the ability to leverage existing business logic for test setup and verification. The author acknowledges the limitations in coverage compared to tools like Playwright but finds the Go-based testing suitable for server-rendered HTML projects like Inkmi. The article concludes with a positive outlook on the results achieved through Go-based web UI testing for the Inkmi project, emphasizing the importance of understanding the trade-offs and suitability of this approach for specific project requirements.
Related
Interface Upgrades in Go (2014)
The article delves into Go's interface upgrades, showcasing their role in encapsulation and decoupling. It emphasizes optimizing performance through wider interface casting, with examples from io and net/http libraries. It warns about complexities and advises cautious usage.
Common Interface Mistakes in Go
The article delves into interface mistakes in Go programming, stressing understanding of behavior-driven, concise interfaces. It warns against excessive, non-specific interfaces and offers guidance from industry experts for improvement.
Serving a billion web requests with boring code
The author shares insights from redesigning the Medicare Plan Compare website for the US government, focusing on stability and simplicity using technologies like Postgres, Golang, and React. Collaboration and dedication were key to success.
Writing GUI apps doesn't have to be painful
The author discusses challenges in developing Windows GUI apps, opting for Go with Fyne library for a smart card reader project. Despite minor drawbacks, Go+Fyne proved efficient, attracting users and contributors.
First impressions of Go 1.23's range-over-func feature
The author shares positive experiences with Go 1.23's range-over-func feature, initially skeptical but finding it easy to use. Successful adaptation in their project Kivik disproved initial concerns, highlighting benefits for codebase improvement.
1 commentsRelated
Interface Upgrades in Go (2014)
The article delves into Go's interface upgrades, showcasing their role in encapsulation and decoupling. It emphasizes optimizing performance through wider interface casting, with examples from io and net/http libraries. It warns about complexities and advises cautious usage.
Common Interface Mistakes in Go
The article delves into interface mistakes in Go programming, stressing understanding of behavior-driven, concise interfaces. It warns against excessive, non-specific interfaces and offers guidance from industry experts for improvement.
Serving a billion web requests with boring code
The author shares insights from redesigning the Medicare Plan Compare website for the US government, focusing on stability and simplicity using technologies like Postgres, Golang, and React. Collaboration and dedication were key to success.
Writing GUI apps doesn't have to be painful
The author discusses challenges in developing Windows GUI apps, opting for Go with Fyne library for a smart card reader project. Despite minor drawbacks, Go+Fyne proved efficient, attracting users and contributors.
First impressions of Go 1.23's range-over-func feature
The author shares positive experiences with Go 1.23's range-over-func feature, initially skeptical but finding it easy to use. Successful adaptation in their project Kivik disproved initial concerns, highlighting benefits for codebase improvement.