docs: reorganize examples directory and fix test issues#453
Merged
Conversation
- Add examples/single/README.md with single-project mode overview - Unify README format across all framework examples (pytest, behave, robot, tavern) - Rename pytest test files to follow test_*.py naming convention - Update multiproject README with DEMO1/DEMO2 project codes - Add comprehensive code examples and documentation links
Rewrite all example tests across frameworks to demonstrate practical usage patterns with meaningful test scenarios: Pytest: - test_basic.py: Auth, shopping cart, password validation, severity levels - test_steps.py: Login flows, checkout, nested steps, data validation - test_attachments.py: JSON/CSV/HTML reports, performance metrics, API logs Behave: - simple.feature: Login, payment, password reset scenarios - suites.feature: OAuth, security, session management with nested suites - parametrized.feature: Role access, email validation, discount calculations - steps.py: Comprehensive step definitions for all scenarios Robot Framework: - simple.robot: E2E flows, API validation, checkout with keyword steps - parametrized.robot: Data-driven tests with templates for validation Tavern: - test_simple.tavern.yaml: CRUD operations, error handling - test_with_id.tavern.yaml: Multi-step flows with data passing All tests now demonstrate: - Realistic business scenarios (e-commerce, auth, API) - Proper use of each framework's Qase annotations - Step tracking and attachment usage - Metadata fields (severity, priority, layer)
- Fix duplicate QaseIDs in Behave features (unique ranges per file): - simple.feature: 1-6 - suites.feature: 100-107 - parametrized.feature: 200-204 - attachments.feature: 300-305 - Fix @Qase.fields syntax: replace spaces with underscores in values - Fix @qase.ignore() to include parentheses (pytest) - Fix @qase.suite() to use dot notation for nested suites - Add missing Behave step definitions for all scenarios - Update .gitignore with qase.lock and Robot Framework outputs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
examples/directory with unified structure (single/andmultiproject/)Changes
Documentation
Test Examples Improvements
Bug Fixes
@qase.fieldssyntax in Behave (replaced spaces with underscores)@qase.ignore()to include parentheses in pytest@qase.suite()to use dot notation for nested suites.gitignorewithqase.lockand Robot Framework outputsTest plan