Access Control Page Visit

Prepared by	Test Scenario for

Prepared by	Test Scenario for
Foivos Polykarpou	Access Control Page Visit

Overview

Title	Test Name	Objective

Title

Test Name

Objective

Access Control Page Visit

accesscontrol.js

1.1. This test verifies the functionality of accessing the access control page of a web application.
1.2. It checks for any errors during the page visit and captures console logs and screenshots for further analysis.

Dependencies Installed: Make sure the required npm packages mentioned in Login with valid and wrong credentials are installed

Install minimist for environment variable (baseURL)
2.1. Ensure that the loginfc.js module is correctly set up and exports the page, browser, and baseUrl objects.
2.2. Ensure that the tenantSwitcher.js module is available and correctly implements the switchTenantSystemAdmin function.
2.3. The chai library should be installed for assertions.
2.4. The test environment should have access to the web application at the specified baseUrl.

npm install puppeteer minimist

4.1. Before Hook
- Capture console logs from the page to monitor any errors or warnings during the test.
4.2. After Hook
- Close the browser to clean up resources after the test execution.
4.3. Test Case: Visit Access Control Page
- Switch Tenant
  - Use the switchTenantSystemAdmin function to switch to the system admin tenant.
- Navigate to Access Control Page
  - Use the page.goto method to navigate to the access control page.
  - Capture a screenshot after opening the page.
  - Verify successful navigation by checking the current URL.
- Log Console Messages
  - Log all console messages to inspect for errors.
4.4. Error Handling
- If an error occurs during the process, capture a screenshot and log the page's HTML content for debugging.

5.1. The test should successfully navigate to the access control page without errors.
5.2. A screenshot should be captured, and console logs should be free of errors.