-
Notifications
You must be signed in to change notification settings - Fork 737
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
c31a3f8
commit 349dee6
Showing
3 changed files
with
33 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
This folder contains the configuration files and scripts that can be used to automate OIDC FAPI conformance testing. These tests can be run using GitHub actions or locally. | ||
|
||
## Testing using GitHub actions | ||
|
||
OIDC FAPI conformance test workflow can be used to for this purpose. | ||
1. Go to Actions tab in your repository | ||
2. Click on FAPI OIDC Conformance Test workflow | ||
3. Click on Run workflow | ||
4. You need to provide the product-is release tag version you want to test (by default, it builds the latest IS by source) | ||
5. Also by default FAPI conformance suite is built from the latest released branch in https://gitlab.com/openid/conformance-suite.git. You can run against a specific conformance suite version also. | ||
6. Set 'Send test results to email' to 'yes' if you want to send test summary to a list of pre-configured email addresses. (default is 'no') | ||
7. Click on Run workflow | ||
8. After tests are completed you can view test results on the test summary page | ||
9. Two types of artifacts are saved after the test execution is completed | ||
- test-logs - a log file is generated for each test plan. This log contains a summary of test cases with failures and warnings | ||
- test-results - a zip file is generated for each test plan. You can use a web browser to view a detailed report of the test plan by extracting this zip file | ||
|
||
An email containing the same test summary will also be sent to a pre-configured list of email addresses. The sender email, password and the receiver emil list are the same as for OIDC action build. If you need to have a seperate receiver email list for FAPI Conformance action, | ||
* Save the list of receiver email as 'FAPI_RECEIVER_LIST' seperated by comma. | ||
|
||
Default configuration is to use Gmail SMTP server. You can change that by modifying `SMTP_SERVER` and `SMTP_SERVER_PORT` in `constants_fapi.py` | ||
|
||
This workflow is scheduled to run daily at 08:30 UTC (2:00 AM SL time) and will also automatically trigger after a release or a pre-release. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters