-
Notifications
You must be signed in to change notification settings - Fork 248
MFTF Process and Increase of Automated Test Coverage
- HipTest is a source of truth for automated test coverage as well as regression testing.
- HipTest scenarios should be extended for components with business cases which are not covered at the moment (this is the most challenging part).
- All test cases in HipTest must be triaged by the Product Owner and the corresponding label which describes priority (S0/S1/S2/S3) should be assigned to them.
- All the test cases which have S0/S1 label assigned is a matter of automation with MFTF.
- For all the S0/S1 scenarios a corresponding GitHub issue should be created. All these issues should have "MFTF (Functional Test Coverage)" label assigned on GitHub.
- Both HipTest scenario and a GitHub issue are interlinked so that HipTest scenario has a reference to GitHub issue and vice versa.
- One GitHub issue corresponds to one and only HipTest scenario, so the relationship between HipTest and GitHub issues is 1-to-1.
It should look like:
GitHub issue has a reference to HipTest scenario and the name of the issue on GitHub is identical to the use-case on HipTest.
The Scenario on HipTest has linkage to GitHub as well
- When a Pull Request created for a given GitHub issue and then the PR is merged we should add label "Automated" to the corresponding HipTest scenario.
It happened that some Folder IDs on HipTest have changed and that lead to the URLs pointing to HipTest scenarios got broken.
For example, let's look at the GitHub issue number: https://github.com/magento/inventory/issues/1360 It refers to HipTest scenario: https://app.hiptest.com/projects/69435/test-plan/folders/432042/scenarios/1446632 (following this URL client currently given an error 400).
- Copy name of the Issue on Github. In this case: "Order with Virtual product on Single stock mode canceled from Admin"
- Go to HipTest and make a search among all test scenarios by this name
- Follow to the first result on the result page We see that link is broken because folder ID has changed - https://app.hiptest.com/projects/69435/test-plan/folders/735224/scenarios/1446632 So that we can update the link on GitHub now.
To verify that HipTest scenario exists on GitHub - the search on GitHub could be applied:
Multi-Source Inventory developed by Magento 2 Community
- Technical Vision. Catalog Inventory
- Installation Guide
- List of Inventory APIs and their legacy analogs
- MSI Roadmap
- Known Issues in Order Lifecycle
- MSI User Guide
- 2.3 LIVE User Guide
- MSI Release Notes and Installation
- Overview
- Get Started with MSI
- MSI features and processes
- Global and Product Settings
- Configure Source Selection Algorithm
- Create Sources
- Create Stock
- Assign Inventory and Product Notifications
- Configure MSI backorders
- MSI Import and Export Product Data
- Mass Action Tool
- Shipment and Order Management
- CLI reference
- Reports and MSI
- MSI FAQs
- DevDocs Documentation
- Manage Inventory Management Modules (install/upgrade info)
- Inventory Management
- Reservations
- Inventory CLI reference
- Inventory API reference
- Inventory In-Store Pickup API reference
- Order Processing with Inventory Management
- Managing sources
- Managing stocks
- Link and unlink stocks and sources
- Manage source items
- Perform bulk actions
- Manage Low-Quantity Notifications
- Check salable quantities
- Manage source selection algorithms
- User Stories
- Support of Store Pickup for MSI
- Product list assignment per Source
- Source assignment per Product
- Stocks to Sales Channel Mapping
- Adapt Product Import/Export to support multi Sourcing
- Introduce SourceCode attribute for Source and SourceItem entities
- Assign Source Selector for Processing of Returns Credit Memo
- User Scenarios:
- Technical Designs:
- Module Structure in MSI
- When should an interface go into the Model directory and when should it go in the Api directory?
- Source and Stock Item configuration Design and DB structure
- Stock and Source Configuration design
- Open Technical Questions
- Inconsistent saving of Stock Data
- Source API
- Source WebAPI
- Sources to Sales Channels mapping
- Service Contracts MSI
- Salable Quantity Calculation and Mechanism of Reservations
- StockItem indexation
- Web API and How To cover them with Functional Testing
- Source Selection Algorithms
- Validation of Domain Entities
- PHP 7 Syntax usage for Magento contribution
- The first step towards pre generated IDs. And how this will improve your Integration tests
- The Concept of Default Source and Domain Driven Design
- Extension Point of Product Import/Export
- Source Selection Algorithm
- SourceItem Entity Extension
- Design Document for changing SerializerInterface
- Stock Management for Order Cancelation
- Admin UI
- MFTF Extension Tests
- Weekly MSI Demos
- Tutorials