Pytest vs Robot, A battle or Co existence
summary
Compares concrete examples: simple GitHub and NASA API status-code tests are implemented in pytest using pytest fixtures and run with the pytest-html plugin to produce reports, then converted into a Robot library by applying Robot decorators so the same Python methods become Robot Framework keywords; tests execute, two pass and two fail as expected. Claims pytest can be about 30% faster (not benchmarked here). Demonstrates minimal-refactor migration and coexistence; code lives in the PyCon GitHub repo.
AI-written summary · about
chapters (24)
- 0:00Introduction and speaker welcome
- 1:22Overview of test frameworks
- 2:26Key features of pytest vs Robot
- 3:09pytest and Robot Framework homepages
- 4:34Test flow comparison
- 6:20Robot Framework keywords and resources
- 8:29Complex test scenario setup
- 9:12Writing a pytest test case
- 11:48Running pytest tests
- 12:30pytest fixtures explained
- 14:20pytest plugins and HTML reports
- 15:47Converting pytest to Robot Framework
- 16:53Robot Framework test structure
- 18:42Running Robot Framework tests
- 19:49Test report comparison
- 20:53Advantages and drawbacks
- 22:18Takeaways and conclusion
- 23:23Q&A session begins
- 23:51Robot specification file logic
- 25:17Robot vs BDD frameworks
- 26:27Generating Robot tests from pytest
- 27:40Requirement engineer perspective
- 29:04HTML report satisfaction debate
- 30:10Coexistence and refactoring
related talks
38mRoman Zakharov: Robot Framework: A Perfect Tool to Get Rid Of
27mWhy I use py.test and maybe you should too
01h 28mTesting with Pytest for Data Science
33mUnit Testing with Pytest
28mEgad! How Do We Start Writing Better Tests?
24mTesting Your Python Code
29mAdopt-a-pytest
21mDon't just test, my friend, test better