Openbravo Issue Tracking System - POS2 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0047947 | POS2 | Core | public | 2021-10-28 16:32 | 2024-07-29 09:39 |
| Reporter | caristu | ||||
| Assigned To | sntgreale | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | scheduled | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | open | ||||
| Review Assigned To | |||||
| OBNetwork customer | No | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0047947: Create test utility component for defining Provider + SessionProvider | ||||
| Description | It is a common pattern in the test cases to have a Provider + a SessionProvider in order to provide both a redux state and a session context for the testing components: <Provider store={store}> <SessionProvider> ... </SessionProvider> </Provider> It would be nice to have a component that encapsulates this pattern in order to ease this kind of component definition and avoid code duplication. | ||||
| Steps To Reproduce | . | ||||
| Proposed Solution | - Create a component that encapsulates the Provider + SessionProvider pattern - Make it use of it in the existing test cases to avoid code duplication | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2021-10-28 16:32 | caristu | New Issue | |||
| 2021-10-28 16:32 | caristu | Assigned To | => Retail | ||
| 2021-10-28 16:32 | caristu | OBNetwork customer | => No | ||
| 2021-10-28 16:32 | caristu | Triggers an Emergency Pack | => No | ||
| 2021-10-28 16:36 | guilleaer | Assigned To | Retail => platform | ||
| 2021-10-28 16:36 | guilleaer | Status | new => acknowledged | ||
| 2022-02-01 08:07 | alostale | Assigned To | platform => Triage Platform Base | ||
| 2022-03-09 14:31 | sntgreale | Assigned To | Triage Platform Base => sntgreale | ||
| 2022-03-09 14:31 | sntgreale | Status | acknowledged => scheduled | ||
| 2022-03-14 19:43 | hgbot | Merge Request Status | => open | ||
| 2022-03-14 19:43 | hgbot | Note Added: 0135708 | |||
| 2022-03-14 19:45 | hgbot | Note Added: 0135709 | |||
| 2022-03-14 19:50 | hgbot | Note Added: 0135710 | |||
| 2022-03-14 19:53 | hgbot | Note Added: 0135711 | |||
| 2022-03-14 19:56 | hgbot | Note Added: 0135712 | |||
| 2022-03-14 19:58 | hgbot | Note Added: 0135713 | |||
| 2022-03-14 20:04 | hgbot | Note Added: 0135714 | |||
| 2022-03-14 21:10 | hgbot | Note Added: 0135715 | |||
| 2024-07-29 09:38 | hgbot | Note Added: 0167418 | |||
| 2024-07-29 09:38 | hgbot | Note Added: 0167419 | |||
| 2024-07-29 09:38 | hgbot | Note Added: 0167420 | |||
| 2024-07-29 09:38 | hgbot | Note Added: 0167421 | |||
| 2024-07-29 09:39 | hgbot | Note Added: 0167422 | |||
| 2024-07-29 09:39 | hgbot | Note Added: 0167423 | |||
| 2024-07-29 09:39 | hgbot | Note Added: 0167424 | |||
| 2024-07-29 09:39 | hgbot | Note Added: 0167425 | |||