This message was deleted.
# hobbyfarm
a
This message was deleted.
c
I have done it many times in the past (in C#), trying to follow best practices (Gherkin/BDD, code generation, Selenium, Page Object). It's a great way to feel confident in the existing application and new development :)
Name proposal: •
HobbyFarm/e2e-testing
HobbyFarm/hobbyfarm-testing
HobbyFarm/automated-testing
Features: • Validate main functionalities of all components: gargantua (REST API calls), ui (web), admin-ui (web) • Run smoke tests (quick tests to make sure the most important behaviors are working, in particular links with external services) • Execute scenarios reproducing end user workflows
f
Yeah that sounds great! I will create a repository for that feature
🙏 1
I only created the License file. You would have to provide a README for a basic description
c
Thank you very much! I'll take more time but it makes more sense to do it in Go and I need to get better at Go anyway 😅
f
Yes go would be nice,so it aligns with gargantua
👍 1
c
Just FYI I initialized a PR, I was off last week so I'm still at the design phase. But I'm update an ADR that is in the branch. https://github.com/hobbyfarm/e2e-testing/pull/1
f
Okey just let me know when it is ready to be merged! 🙂
👍 1