Developer Testing
Confirmation of Standards Adherence
Activity | Date Tested | Notes |
| N/A | |
| N/A | |
| N/A |
Developer Tests and Outcomes
Notes:
"enabling a user" means granting a staff member the 'eProcurement user' permission in eAuthorisations, and at least one cost centre and job code.
Ideally, for end to end testing, the input for each test should be configuration of user(s) in eAuthorisations, and the result should be confirmed changes in the SciQuest application. However, there is no SciQuest application for dev environment, so the POST step is disabled. As a workaround, the generated XML can be manually POSTed to SciQuest Test, or inspected to verify to changes are included. All generated XML must be valid against its DTD, or it should be marked as a fail.
Users
Test | Outcome | Notes/JIRA |
Enabling a new user for the first time: They are created in SciQuest with status 'Pending' | Pass | |
Disabling a user: Their status is set to 'Inactive' | Pass | |
Disabling a user: Their codes are removed | Pass | |
Enabling an existing (inactive) user: Their status is set to 'Active' | Pass | |
New and changed existing users have the following properties set: | ||
- FirstName (value from eAuth) | Pass | |
- LastName (value from eAuth) | Pass | |
- UserStatus ('Active', 'Inactive' or 'Pending') | Pass | |
- Email (value from eAuth) | Pass | |
- TelephoneNumber | ||
- CountryCode (fixed value: 44) | Pass | |
- AreaCode (fixed value: 0131) | Pass | |
- Number (value from eAuth) | Pass | |
- Limits | ||
- PurchasingRequisitionLimit (value from eAuth: 'eFinancials Purchase Ordering') | Pass | |
- PurchasingLineLimit (value from eAuth: 'eFinancials Purchase Ordering') | Pass | |
- ApprovalPOTotalLimit (value from eAuth: 'eFinancials Purchase Ordering') | Pass | |
New users have the following properties set: | ||
- AuthMethod (fixed value: SAML) | Pass | |
- International | ||
- Language (fixed value: en) | Pass | |
- Country (fixed value: GB) | Pass | |
- Timezone (fixed value: Europe/London) | Pass | |
- Currency (fixed value: GBP) | Pass | |
- PreferredEmailFormat (fixed value: HTML) | Pass | |
An existing user with no changes in eAuth since last run is not included in import | Pass | |
An existing user with changes to any basic user properties (name, email, phone) is included in import | Pass | |
An existing user with a change to 'eFinancials Purchase Ordering' limit is included in import | Pass | |
An existing user with any changes to cost centres and/or job codes is included in import | Pass | |
An existing user with no changes in eAuth, but who owns a code which is impacted by changes to codes in eFin, is included in import. | Pass | |
Imported user codes correctly reflect what is set in eAuth (including qualifying common codes and minus unpostable codes) | Pass | |
XML file is not POSTed to SciQuest if there are no user changes | Pass |
Codes
Test | Outcome | Notes/JIRA |
Activating codes: Any cost centre, job code which is being imported for a user, is also included in the import and made active if it does not already exist or is inactive | Pass | |
Inactivating codes: Any existing cost centre, job code which exists and is active, is made inactive if the result of a user import means that the code is no longer presently owned by any active users | Pass | |
Adding code pairs: Any postable codepair which is possible due to activation of codes or changes to eFin posting rules, is added | Pass | |
Removing code pairs: Any codepair which is no longer valid due to inactivation of codes or changes to eFin posting rules, is removed | Pass | |
Changing an active code's name in eFin will include that updated code in the import | Not Tested | |
XML file is not POSTed to SciQuest if there are no code changes | Pass |
Performance
Test | Outcome | Notes/JIRA |
The process completes in a reasonable amount of time when there are small changes | Pass | |
The process completes in a reasonable amount of time when there are large changes | Advisory | PPS008-41 |