Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

This page houses documentation related to:

  • Dev Testing, and
  • Self Walkthrough

Self walkthroughs are (normally) done prior to (scheduled) walkthrough with the functional lead, stepping through various combinations of the potential path the application can take, toggling certain conditionals (which expose additional fields), going over the functionality that will be demonstrated in the walkthrough with the functional lead, etc.

If any aspect of the application is not functioning as intended, it will be logged here and it should be mentioned to the customer first thing / at the start of the meeting.

Dev Testing on  —  

Path/Combination Tested

Initial Submission → HR → Employee → Supervisor → AR for Supervisor → Manager → AR for Manager → HR → HR Specialist

Tasks Being Tested

#13 & #14:   -  

#6 & #7: ,  

Notes

#Outcome

1 

"Manager Review Section" was not showing AT the "Manager Review" stage

  • This behavior was rectified; cause: "Send back to Employee" field was hidden... the rule that exposed this section required that "Send back to Employee" is set to "No" — however, in a hidden state, the value of the field (as far as the rule is concerned), is neither "No" nor "Yes" — so the fix was as simple as making that field visible
2

The "Date Completed" was getting prefilled AS SOON AS the form was opened by HR (in the "HR Review" Stage); this is problematic... because what if the user selects one of the "No - Send to ...." option instead of "Yes"?

  • This behavior was rectified, by logging the "Date Completed" only when the user selects "Yes" — each of the other options for "Is this form complete?", will blank-out / reset this field
3

HR Role cannot cancel, at the "HR Review" stage, as the form complains about the "Comments for..." boxes being empty... (which aren't shown unless it's corresponding selection is made in the "Is this form complete?" question.... 

  • This behavior was rectified by making all comment boxes "not required" by default, and toggling it's required state programmatically

4

For the longest time, the calculation table fields (i.e. Effective Date, Annual Salary as of, etc.) had no labels... this posed two problems:

  1. When adding these fields to rules, one needed to know the IDs of fields to be added, which becomes tedious as you are constantly switching back and forth between the Rules UI and going into the field's (that needs to be added to the rule) properties
    to grab it's ID.
    • So we are going to add the label and then use CSS to hide those labels.
  2. The red asterisk "*" before the field didn't show, even though in the Leap UI, it's shown...This is because we used "empty" label (i.e. the input field was created and no label was provided).
    • To fix this, we will (yet again) use CSS to add an asterisk in the beginning of the "text" field (i.e. as a prefix)
BeforeAfter

Currently (prior to doing the above), here's how the retroactive calculation table looks. The boxes outlined should have a * indicator... as they are indeed required:

Here's how it looks now (smile)





5

If HR is cancelling the form at the "Under Review by HR Specialist" stage, hide the "Send back to HR" and "CLOSE OUT" buttons.... actually, confirm with Functional Lead: we need to get rid of the "Send back to HR" submit button right (since the purpose of that was so that the Salary/GWI/Merit info can be updated)?

BeforeAfter

We need to keep the button because:
In the event that the wrong HR Specialist team member was assigned, the application can be sent back to the "Under HR Review" stage, where the HR Role team member can assign the correct HRS Team member

6

There is an inconsistency with submit buttons:

  • On some stages, we are hiding the "submit button" (e.g. "Submit for Manager Review") and only showing it once all criteria for being able to submit are met, whereas
  • On others we are showing the button, however it is disabled until all criteria for being able to submit are met, at which point the button is enabled

I recommend that all buttons be shown, but disabled, until all criteria for being able to submit are met! (the latter is more prevalent than the former... so it is also quicker to get done!)

7

All emails & ACMs include HR's logo from the phptst1 server... make sure to switch the image URL to the FEB central server.

NOTE: HR logo appears in all emails and ACMs etc. as it should right now... this just future-proofs it!

8

While the email preview shows how the body of the email will look like, it does not show the following—

  • To
  • Cc
  • Subject

Proposing the following—

Instead ofWe do


NOTE: the above 'We do' is merely a mock-up!

Testing Results (After Addressing a Task)

Tasks #12, 13, & 14

Form #Applies to Task#StageResult
10612 & 13HR Form Received



10812 & 13Under Employee Input



12612 & 13Under Review by Supervisor



12712 & 13Under Review by Additional Reviewer for Supervisor



10912 & 13Under Review by Manager



12812 & 13Under Review by Additional Reviewer for Manager



11012 & 13Under Review by HR



12912 & 13Under Review by HR Specialist



13014Under Review by HR
SelectionBehaviorBehavior AFTER Providing Comments
NO SELECTION
N/A
No - Send to Employee
No - Send to Supervisor
No - Send to Additional Reviewer for Supervisor
No - Send to Manager
No - Send to Additional Reviewer for Manager
Yes
N/A


1306

Currently, here's how the preview looks (prior to applying any fixes/etc.)

BeforeAfter






Dev Testing on  

At the start of the walkthrough, the above points were disclosed to the customer; in addition, it was mentioned that  I  took full onus on it not functioning as intended (especially #1, above)

#Outcome

1 

Employee lookup within a table for "Do you have formal supervisory responsibilities for any other UConn employees?" was not working.

  • This  was  previously reported by the customer, however because I always took the shortest path in my prior testing (i.e. the table shows only if you answer "Yes" to the question and I always had selected "No") this was not noticed.
2

Ability for the HR Role to cancel the form at any stage (after the initial submission stage) feature has been working....  HOWEVER , HR cannot cancel if the "Required" fields were not filled-out... prior to the walkthrough, I came up with a fix for it and the fix was implemented for the second stage.... the rest of the stages needed the same fix applied to them






  • No labels