I extensively use robot framework and python everyday, currently for APIs using requests library for python, for actual api calls etc. Tests are in robot and is incredibly easy to understand. Robot also has great community support and documentation. I’ve used robot a lot for UI automation too. Great libraries out there to use with robot for this are selenium and playwright. Start with selenium as I think more people use that. Robot gives you inbuilt reporting too in html so no worries there. You’d definitely need to learn some basic python when it comes to API, for UI, with robot framework you won’t need to learn anything has robot framework is a text based language as well. Once you deep dive into docs and how to use you’ll how easy it is, especially to start things up. Good luck ! More on reddit.com

Selenium can be invoked within pytest to test a custom website's functionality. You can write function/integration tests that actually access the page you wrote and interact with it, then verify the result is what you expected. Whether that's a good idea is a topic of debate. I can say from experience that such tests tend to be extremely slow for automated tests, and it takes a lot of dedication to keep them from breaking as you make changes. The only way it could be used to test your code that uses Selenium is to invoke your code and then either examine the response or perform a second request to assert it created, updated, or deleted the data you expected. Unless you have access to a staging/testing copy of the system it accesses, though, that would be a bad idea. You don't want to create dummy test data in production. You also face the problem that your code depends heavily on the website. This means that as it changes, your scripts will break. A test suite can help detect those cases when those changes happen, but both your code and its tests are at the mercy of the maintainers. A more common approach would be to unit test the parts of your system that don't absolutely require external dependencies. This would include things like processing you do on the response of a web request before sending a second one. Writing these kinds of tests requires you to organize your code such that this logic lives in functions and methods that don't access the website directly; they would take any data from external sources as a parameter instead. (You could use mocks to simulate making the web requests and obtaining the data, but that makes your tests more brittle and harder to maintain and provides no advantages compared to separating the logic out. You'll still see people recommending it, though.) But given the description of your use case, though, you may not have any logic like that. More on reddit.com