Please enable JavaScript.
Coggle requires JavaScript to display documents.
ClubGRANTS API Integration - Coggle Diagram
ClubGRANTS API Integration
My findings and Notes
Test Scenarios
How a draft application is displayed in Reports
How a submitted application displayed in application
How a submitted application in Reports
How a submitted application is allowed to be edited in Application
Authrisation related test scenarios
Why
Need to validate multiple test scenarios to ensure security in place
Again we have not done extensive testing on this front so need to go through a proper test phase
How a draft application is displayed in application
Check with Brad
Is it ok to establish that we need time to test end to end flow to make sure everything flows correctly
This could be internal testing but with a actual third party integrating we want to take this opportunity to test this thoroughly
Could be this considered as something we should have already done
Is this OK to be communciated to ClubNSW as the scope
Different types of testing
Validation testing
Tests to validate that API is developed based on the specs given
What needs to be included here?
Security Testing
What kind of testing needs to be included
Functional testing
End to end flow will come here
Load Testing
What is the scope for tihs
We advice the final goal/ target to be considered here rather than leaving to test it at a later stages
Run Time and error detection
Make sure the errors are captured and logging is adequate
ClubNSW Discussion
Resolve all remaining issues
Establish a common team and common time slot to work on testing
Understanding the test scope
Share the test plan
Go through the UI again as we could not complete again together
Understand the plan to fix the forms
What is the plan to have proper UI forms
UI Level scenario walk throughs
Multiple users
Multiple venues
Data setting up
Authentication related scenarios
What is the plan for UI Forms
Questions from team
When will be the form will be developed
Only the UI from Dev side is developed
Su
Application is edited by Regular
Authentication
Who created it who submitted need to be displayed
Authentication
CMAC
Synchronised steps
Whether these things come in right steps
Their front end steps
Field validations are in place in the API
How their UI response
Get end to end testing
Their screens needs to be tested
Types of testing to be done
ClubNSW UI Level Testing
This is more of a consultative input to them
We advise them about the controls, validations they should have in their end to make sure that they do not come across the Validation errors that will be thrown from API side
The validations they should be having in their UI forms
ClubNSW API integration testing - This is the piece you started doing and continue to do this piece
Include that synchronising scenario which will have to the thought of
Security Testing ( Authentication related testing )
What kind of testing we need to perform in our end that will make sure the authentication is taken care of
Right now we may only have only the high level items but will start from that and elaborate
End to end testing ( Internal)
We should make use of all clubGRANTS testing resources here
We will have to make sure we validate all test scenarios that was validated end to end including CMAc
Just realised should we consider things such as
Load testing
Validating how logging and alerting performed..