[PM] 10-10EZ - Household Optimization: Complete QA on the new changes

[hdjustice]

Background

Ad development wraps up, we need to begin QA on the changes to the Household section of the 10-10EZ

Resources

• FE Ticket #52960
• Use cases
• Staging Review preparation guidance
• QA Standards guidance
• TestRail Test Runs

Tasks

• [ ] Coordinate QA schedule
• [ ] Use TestRail to perform QA, using test cases/test runs to track and document results
• [ ] Communicate any defects found to the team for resolutions
  • May need create tickets for these
• [ ] Generate the following artifacts (after defect resolutions and retesting):
  • Regression test plans - Ticket #51645
  • Accessibility test plan - Ticket #51644
  • Household section optimization Test plan
  • Coverage for References
  • Summary(Defects) reports
  • E2E tests (provide a link to the product’s code)
    • These are the engineer's End-to-end testing, but we also have a ticket with Stakeholders for further End-to-end testing)
  • Code coverage (provide a link to the product’s code)

Acceptance Criteria

• QA is fully completed before Staging review

[hdjustice]

Test Case B: the Financial Disclosure prep page lists "2022" (twice) - Is the expectation that this needs to be updated every year? ANSWER: Yes, this will require annual updates. This was to address the uncertainty and ambiguity around "Last year's" or "Last calendar year" references

[hdjustice]

Use Case C: The Spousal financial support question is prompting, even though I answered YES that the spouse lived with the Veteran last year and has the same address

[jessicastump]

I put some content edits found so far during a first review of staging and new content edits that we have still been getting to this ticket: [FE] 10-10EZ Content changes household section - Post QA #57959 Let me know if I should put edits here and keep that ticket only for new things the content team gives us.

[hdjustice]

@jessicastump - No, let's keep those content edits in that ticket. This one can be for functionality defects. I could actually move my "bold" comments to that ticket

[mkerns1]

#	Test Case ID	Test Description	Pass/Fail	Bug ID (if any)	Comments
A	TC-A	Applicant does not want to disclose their financial information	Pass		On the confirmation step, the button says "Confirm" not "continue.
B	TC-B	Applicant wants to disclose their financial information, is not married, and has no dependents	Pass		Looks good to me!
C	TC-C	Applicant wants to disclose their financial information, is married, and has no dependents; lives with spouse	Pass	BUG-001	When selecting yes to both spouse questions the next step in the form indicates conflicting information. I selected "yes" i lived with my spouse all of 2022 and the next step is the spouse's financial support. BUG TICKET #59034 created. UPDATE: BUG TICKET #59034 Resolved.
D	TC-D	Applicant wants to disclose their financial information, is married, and has no dependents; does not live with spouse, does not provide financial support	Pass		Why are the Income data points note formatted but the Deductible expenses data points are? ADDED This finding to #57959 content ticket
E	TC-E	Applicant wants to disclose their financial information, is married, and has no dependents; does not live with spouse, does provide financial support	Pass		Looks good to me!
F	TC-F	Applicant wants to disclose their financial information, is married, and has two dependents; lives with spouse	Pass	BUG-002	After adding Dependents Annual Income information and clicking continue the form breaks and reveals this error message in the console: instrument.js:109 TypeError: Cannot read properties of undefined (reading 'first'). BUG TICKET #59041 created. UPDATE: BUG TICKET #59041 Resolved.
G	TC-G	Applicant wants to disclose their financial information, is married, and has at least one dependent; does not live with spouse, does not provide financial support	Pass	BUG-002	After adding Dependents Annual Income information and clicking continue the form breaks and reveals this error message in the console: instrument.js:109 TypeError: Cannot read properties of undefined (reading 'first') UPDATE: BUG TICKET #59041 Resolved.
H	TC-H	Applicant wants to disclose their financial information, is married, and has at least one dependent; does not live with spouse, does provide financial support, does not live with dependent, does provide financial support	Pass	BUG-002	After adding Dependents Annual Income information and clicking continue the form breaks and reveals this error message in the console: instrument.js:109 TypeError: Cannot read properties of undefined (reading 'first') UPDATE: BUG TICKET #59041 Resolved.
I	TC-I	Applicant wants to disclose their financial information, is not married, and has at least one dependent	Pass	BUG-002	After adding Dependents Annual Income information and clicking continue the form breaks and reveals this error message in the console: instrument.js:109 TypeError: Cannot read properties of undefined (reading 'first') UPDATE: BUG TICKET #59041 Resolved.

[jessicastump]

I went through the form a couple of times (most cancelled out in error mentioned below, but was able to submit one app successfully with one dependent) and could not replicate error below on screen but realizing the note said "is in console"...so perhaps it was occurring.

message in the console: instrument.js:109 TypeError: Cannot read properties of undefined (reading 'first')

What I did encounter: when in the modals and canceling adding/editing a dependent, the page would blank out and I would have to start the application over. See screenshot below.

Additional notes

• Confirming BUG-001 on the spouse information and the financial support question should only show when No is selected for having the same address question.
• Child educational expenses: Can the page be conditional based on birthdate entered? Since it is referring to a specific age range in the question. Ticket #59395 created for this change
• Odd things with date input - noticed some numbers on years and such changing and jumping around after input (using mac laptop, keyboard and tab and trackpad to navigate)

[hdjustice]

We have had reports from previous research participants that the date numbers jump around/change unintentionally after input. We haven't talked much about the "Memorable date" component, but I think we might have decided that it would be a whole-form change and should not be part of this work.

[hdjustice]

and to confirm that the "blank" screen (that you captured above) is what @mkerns1 described exactly. It appears we have a few bugs to create here. I will work on that this week and we can review next week when @longmd returns.

[jessicastump]

Ticket #59397 created for this change

The card used for reviewing dependents has some changes needed, see notes from Design Council meeting (note, no final decision or next steps were listed). Experimental Ticket

Updated image below. DSC guidance to not horizontal align as items on the right are often missed with magnification settings. Design updates include a stacked mobile friendly layout:

In staging:

[hdjustice]

Ticket #59296 created for this BUG

Use Case F:

• I entered the second dependent, on that page i mistyped the birth month and corrected it on the same screen, however the subsequent screens are prompting me with an error on a field I have only just now seen. Could this be due to the URL not changing for the dependent info?

• 

• 

• 

[hdjustice]

QUESTION: (ANSWERED in comment below this one) If the dependents are edited, originating from the Review Page, and the applicant DOES NOT hit the Update Page button on the Review page after making edits, do they take affect still or revert back to the original input?

[longmd]

QUESTION: If the dependents are edited, originating from the Review Page, and the applicant DOES NOT hit the Update Page button on the Review page after making edits, do they take affect still or revert back to the original input?

@hdjustice , the edits do take place. The "Update Page" button simply takes that field out of edit mode. The edits are already committed once you come back to the review page.

[hdjustice]

Ok cool, I was thinking about folks who may not notice that Update page button as something to be done. Thank you!

[hdjustice]

All QA has been completed and all defects have been resolved.