Skip to content

Jans Pre Release Test Plan

manoj suryawanshi edited this page Mar 23, 2023 · 5 revisions

Test Plan Document

Product Name: JANS-CLI

  • Product Line Portfolio: Identity and Access Management Platform

Introduction

Purpose of The Test Plan Document

Purpose of test plan document is to provide details on how testing process
will be conducted for a given project.Its intended audience is the project manager,
project team, and testing team.

SMOKE/CONFIGURATION/COMPATIBILITY Testing

Compatibility test is an assessment used to ensure a software application is 
properly working across different databases,operating systems (OS), networks and 
hardware.Compatibility testing is carried out to check the applications compatibility
with different operating systems such as EL8,Ubuntu,Suse etc  using VM’s ,K8s.

# Item to Test Test Description Responsibility
1 RHEL8 install/configure JANSSEN on RHEL8
2 SUSE 15 Install/configure JANSSEN on SUSE
3 UBUNTU Install/configure JANSSEN on UBUNTU
4 Installation Installation Verification
Verification

SANITY TEST

  1. JANS - TUI

# Item to Test Test Description
1 Attribute 1 Gets a list of attributes
2 Add/update/delete/partially modify a new attribute
2 Default 1 Gets default authentication method
Authentication Method 2 Updates default authentication method
3 Configuration - Properties 1 Gets all Jans authorization server configuration properties
2 Partially modifies Jans authorization server Application
configurationproperties
3 Returns persistence type configured for Jans authorization server
4 Configuration - Fido2 1 Gets Jans Authorization Server Fido2 configuration properties
2 Updates Fido2 configuration properties
5 Configuration - SMTP 1 Returns SMTP server configuration
2 Adds SMTP server configuration
3 Updates SMTP server configuration
4 Deletes SMTP server configuration
5 Test SMTP server configuration
6 Configuration - Logging 1 Returns Jans Authorization Server logging settings
2 Updates Jans Authorization Server logging settings
7 Custom Scripts 1 Gets a list of custom scripts
2 Adds a new custom script
3 Updates a custom script
4 Deletes a custom script
8 OAuth - OpenID Connect - Clients 1 Gets list of OpenID Connect clients
2 Create new OpenId connect client
3 Update OpenId Connect client
4 Get OpenId Connect Client by Inum
5 Delete OpenId Connect client
6 Update modified properties of OpenId Connect client by Inum
9 OAuth - Scopes 1 Gets list of Scopes
3 Updates existing Scope
5 Delete Scope
6 Update modified attributes of existing Scope by Inum
10 SCIM - User Management 1 Gets list of SCIM users
2 Create a SCIM user
3 Retrieves SCIM user by Id
4 Updates an SCIM user
5 Deletes a SCIM user
6 Patches SCIM User attributes
7 Search SCIM user
11 SCIM - Config Management 1 Retrieves SCIM App configuration
2 Partially modifies SCIM App configuration

  1. Integration testing Flow:

# Flows to Test Test Description
1 enable fido2
2 enable 2FA
3 enable otp
4 auth server client test test auth server client
5 Services start/stop/restart all the services and container

  1. JANS-CLI testing
Test JANS-CLI with All command line options for all products

  1. API testing

Test Approach(s)

Follow instructions given on wiki page to install and configuration
of JANSSEN application on different operating system.
    Install application on VM server with given hardware size.

Test Regulatory / Mandate Criteria

Test Pass / Fail Criteria

test passed without any error.

Test Entry / Exit Criteria

Installation and configuration is Successful

Test Deliverables

Test case PASS/FAIL

Test Suspension / Resumption Criteria

Installation and configuration successful.

Test Environmental

SYSTEM AND INTEGRATION TESTING

Test Risks / Issues

It ensures that internal modules and components communicate properly.
It performs regression testing on important connection points.

Items to be Tested / Not Tested

ITEMS TO BE TESTED: JANS-CLI

Test Approach(s)

Install JANS-CLI on differenct OS.
Configure setup.
Run above all Test scenarios manually.
Run above Test scenarios using menu driven interaction mode.

Test Regulatory / Mandate Criteria

Test Pass / Fail Criteria

Test case PASS

Test Entry / Exit Criteria

Entry: New Jenkins build passed
Exit: test case pass

Test Deliverables

TEST case PASS/FAIL report

Test Suspension / Resumption Criteria

Errors occurred during testing

Test Environmental

VM machine with different OS ( ubuntu20, suse 15, RHEL8).
K8s/Minikube.

Test Plan Approval

The undersigned acknowledge they have reviewed the document and agree with
the approach it presents. Any changes to this Requirements Definition will be
coordinated with and approved by the undersigned or their designated
representatives.
Signature:
Date:
Print Name:
Title:
Role:

Appendix A: References

The following table summarizes the documents referenced in this document.

| \#  | DocumentName andVersion | Description | Location         | 
| --- | ----------------------- | ----------- | ---------------- |
| 1   |                         |             |                  |

Appendix B : Key Terms

The following table provides definitions for terms relevant to this document.

| \#  | Term       | Definition | 
| --- | ---------  | ----- -----|
| 1   |            |            | 
Clone this wiki locally