Skip to content
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.

Sign up for GitHub

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

feat: XSB authentication cleanup #255

Merged
merged 3 commits into from
Nov 14, 2024
Merged

feat: XSB authentication cleanup #255

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5386508
feat: Authentication.feat cleanup
Roebot926 Nov 5, 2024
afb8f63
adjustments
Roebot926 Nov 8, 2024
d731e0a
adjustments + SevTags
Roebot926 Nov 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 29 additions & 21 deletions cypress/TestCases/FireboltCertification/Authentication.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,37 +5,45 @@ Feature: Authentication
Given the environment has been set up for 'Authentication' tests
And 3rd party 'certification' app is launched

@sdk @transport
Scenario Outline: Authentication.token - Positive Scenario: <Scenario>
@sdk @transport @Sev0
Scenario Outline: Authentication.token - Validate API Method response for <Scenario>
When '3rd party app' invokes the 'Firebolt' API to '<API_Key>'
Then 'Firebolt' platform responds with '<Validation_key>'

Examples:
| Scenario | API_Key | Validation_key |
| Get Platform token type | get the authentication token for platform | platform authentication token |
| Get Device token type | get the authentication token for device | decode base64 authentication token |
| Get Distributor token type | get the authentication token for distributor | decode base64 authentication token |
| Get Distributor-CIMA token type | get the authentication token for distributor_CIMA | decode base64 authentication token |
| Get Distributor-OAT token type | get the authentication token for distributor_OAT | decode base64 authentication token |

@sdk @transport
Scenario Outline: Authentication.<Method> - Positive Scenario: <Scenario>
| Scenario | API_Key | Validation_key |
| Platform token type | get the authentication token for platform | platform authentication token |
| Device token type | get the authentication token for device | decode base64 authentication token |
| Distributor token type | get the authentication token for distributor | decode base64 authentication token |

@sdk @transport @Sev1
Scenario Outline: Authentication.token - Validate API Method response for <Scenario>
When '3rd party app' invokes the 'Firebolt' API to '<API_Key>'
Then 'Firebolt' platform responds with '<Validation_key>'

Examples:
| Scenario | API_Key | Validation_key | Method |
| Get Device token type | fetch device token | authentication device | device |
| Get Session token type | fetch session token | authentication session | session |
| Get Root token type | fetch root token | authentication root | root |
| Scenario | API_Key | Validation_key |
| Distributor-CIMA token type | get the authentication token for distributor_CIMA | decode base64 authentication token |
| Distributor-OAT token type | get the authentication token for distributor_OAT | decode base64 authentication token |

@sdk @transport
Scenario Outline: Authentication.token - Negative Scenario: <Scenario> expecting error
@sdk @transport @Sev0
Scenario Outline: Authentication.<Method> - Validate API Method response for <Scenario>
When '3rd party app' invokes the 'Firebolt' API to '<API_Key>'
Then 'Firebolt' platform responds with '<Validation_key>'

Examples:
| Scenario | API_Key | Validation_key |
| Invalid Parameter Platform1 | get token with platform1 parameter | invalid parameter error authentication token |
| Invalid Parameter type Boolean | get token with true parameter | invalid parameter error authentication token |
| Invalid Parameter type Integer | get token with integer parameter | invalid parameter error authentication token |
| Scenario | API_Key | Validation_key | Method |
| Device token type | fetch device token | authentication device | device |
| Session token type | fetch session token | authentication session | session |
| Root token type | fetch root token | authentication root | root |

@sdk @transport @Sev1
Scenario Outline: Authentication.token - Validating API Error handling when given <Scenario>
When '3rd party app' invokes the 'Firebolt' API to '<API_Key>'
Then 'Firebolt' platform responds with '<Validation_key>'

Examples:
| Scenario | API_Key | Validation_key |
| invalid parameters for Platform1 | get token with platform1 parameter | invalid parameter error authentication token |
| invalid parameters with type Boolean | get token with true parameter | invalid parameter error authentication token |
| invalid parameters with type Integer | get token with integer parameter | invalid parameter error authentication token |
Loading