-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2025-01-13] [$250] Implement tests for reports that should not be displayed in LHN #52034
Comments
Triggered auto assignment to @alexpensify ( |
Moving to Weekly since we are on hold for App#52036 Heads up, I will be offline until Tuesday, November 12, 2024, and will not actively watch over this GitHub during that period. |
Still on hold for App#52036 |
On hold |
ProposalPlease re-state the problem that we are trying to solve in this issue.Implement tests for reports that should not be displayed in LHN. What is the root cause of that problem?This is the first time we're adding these tests. What changes do you think we should make in order to solve the problem?Example of 1 test for reference: it('should not display hidden report', async () => {
// When the SidebarLinks are rendered.
await LHNTestUtils.getDefaultRenderedSidebarLinks();
const report = createReport({isHidden: false});
// And a non-hidden report is initialized in Onyx.
await initializeState(false, {
[`${ONYXKEYS.COLLECTION.REPORT}${report.reportID}`]: report,
});
// Then the report should appear in the sidebar.
expect(getOptionRows()).toHaveLength(1);
// When the report is hidden.
await act(async () => {
await Onyx.merge(`${ONYXKEYS.COLLECTION.REPORT}${report.reportID}`, {isHidden: true});
});
// Then the report should not appear in the sidebar.
expect(getOptionRows()).toHaveLength(0);
}); A few more can be found on my test branch. It also includes fixes for console errors that appeared while running these tests, e.g. missing Todo: check not only for the count of reports but also validate the name, etc. |
@alexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Job added to Upwork: https://www.upwork.com/jobs/~021862798689700375032 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
📣 @c3024 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @mkzie2 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@luacmartins happy to keep this one, I think you got assigned before I was out for christmas lunch |
@mkzie2 what is youer ETA for the PR? |
Will complete it today. |
This comment was marked as outdated.
This comment was marked as outdated.
Weekly Update: PR is moving along through the review process |
Update: Waiting for this one to go into production Heads up, I will be offline until Friday, January 3, 2025, and will not actively watch over this GitHub during that period.If this GitHub requires an urgent update, please ask for help in the #expensify-open-source Slack Room. If the inquiry can wait, I'll review it when I return online. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.80-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-01-13. 🎊 For reference, here are some details about the assignees on this issue:
|
@c3024 @alexpensify @c3024 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Tracking issue: #52031.
Develop and implement tests to verify that the following report types are not displayed in the Left-Hand Navigation (LHN):
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @alexpensifyThe text was updated successfully, but these errors were encountered: