★

European Commission

Simplifying complex data for better insights

Press Ctrl+I for User Guide

PSO Weekly Testing Reports

Select a testing discipline to view detailed reports and metrics

Manual Testing

Test execution summary, coverage analysis, defect tracking, and usability testing results.

Automation Testing

Comprehensive automation test execution, coverage analysis, and framework performance metrics.

Static Code Analysis

SonarQube metrics, code quality, security vulnerabilities, code smells, and technical debt assessment.

Quality Assurance

SonarQube metrics, code coverage analysis, technical debt, and quality gate status.

Security Testing

Vulnerability assessment, SAST/DAST results, penetration testing, and security compliance.

Performance Testing

Load testing results, stress testing analysis, and performance optimization recommendations.

PSO Reports User Guide

Complete guide to using and managing PSO weekly testing reports

Getting Started

Learn the basics of navigating and viewing reports

Accessing Reports

Click on any report card from the dashboard to open that specific report
All reports are available as standalone HTML files that can be viewed in any modern browser
Reports are automatically updated through the GitLab CI/CD pipeline

Keyboard Shortcuts

Ctrl+I - Open this User Guide (available only on dashboard)
Ctrl+A - Open Admin Modal (requires password, available in reports)
Ctrl+D - Mark all comments as resolved (requires password, available in reports)
Esc - Close modals and dialogs

Accessing User Guide: Click the blue help button (?) in the bottom-right corner or press Ctrl+I from the dashboard to open this guide anytime.

Tip: All reports use the same navigation and functionality patterns, making it easy to switch between different testing disciplines.

Data Collection & Updates

How data is collected and reports are generated

Automated Data Collection

Reports are automatically generated through the following process:

JIRA Data: Python scripts fetch test execution data, bug counts, and metrics from JIRA using REST API
GitLab Data: Test results, pipeline status, and code changes are collected from GitLab
SonarQube Data: Code quality metrics, security vulnerabilities, and technical debt from SonarQube API
JSON Storage: All collected data is stored in JSON files located in reports/json_collector/

Update Frequency

Reports are generated weekly through scheduled GitLab pipelines
Manual updates can be triggered through the Admin Modal (see Pipeline Runner section)
Data reflects the current week's testing activities

Dynamic Updates: When you modify JIRA queries in the Admin Modal, the pipeline automatically uses the new queries for the next data collection cycle.

Adding & Managing Comments

How to add, edit, and publish comments

Adding New Comments

Look for the "+ Add Comment" button in any report section
Click the button to open a rich text editor
Type your comment using the formatting toolbar (bold, italic, lists, etc.)
Click "Save" to save locally or "Save & Publish" to commit to GitLab

Editing Comments

Hover over any comment to reveal the Edit button
Click Edit to modify the comment
Use "Save" for local changes or "Save & Publish" to commit

Deleting Comments

Individual Delete: Click the Delete button on any comment to remove it
Mark All as Resolved: Press Ctrl+D to mark all comments as resolved (requires password)
Bulk Delete: Use Admin Modal → Remove All Comments option to permanently delete all comments (requires password)

Publishing Changes

"Save": Stores changes locally in browser (temporary)
"Save & Publish": Commits changes to GitLab repository (permanent)
Published comments are visible to all users viewing the reports

Important: Local changes (not published) are stored only in your browser and will be lost if you clear browser data.

Admin Modal Features

Advanced settings and management tools

Accessing Admin Modal

Press Ctrl+A from any report page
Enter the admin password when prompted
The Admin Modal will open with 5 main options

Password Required: For security reasons, admin passwords are not displayed in this guide. Contact your project administrator for access credentials.

Option 1: Sections Visibility Control

Show or hide entire sections of the report:

Toggle checkboxes to show/hide main sections and sub-sections
Changes are saved locally and persist across sessions
Click "Save Changes" to apply visibility settings
Use "Reload" to reset to saved settings

Option 2: JIRA Queries Editor

Customize JIRA queries used for data collection:

View and edit current JIRA queries for each section
Modify "Custom Query" textarea to change the JQL (JIRA Query Language)
Click "🔗 Open JIRA" to test the query in JIRA directly
Click "🔄 Revert" to restore default query
"Save Queries" commits changes to JSON file and GitLab
New queries are used in the next pipeline run

Option 3: Remove All Comments

Permanently delete all comments from the current report:

Enter admin password to confirm
Click "Delete All Comments"
Confirm the action in the popup dialog
⚠️ Warning: This action cannot be undone and permanently removes ALL comments!
Note: This is different from Ctrl+D which only marks comments as resolved

Option 4: Run Pipeline

Manually trigger a new report generation:

Click "🚀 Start Pipeline" to trigger GitLab CI/CD pipeline
Monitor progress in real-time through the console output
Pipeline generates ALL reports (Automation, Manual, Security, etc.)
Click "⏹️ Stop Pipeline" to cancel the running pipeline
Use this when you need fresh data outside the scheduled weekly run

Option 5: Restore Deleted Fields

Recover previously deleted editable fields:

View list of all deleted fields with deletion timestamps
Click "Restore" next to any field to recover it
Restored fields appear back in their original sections

Pro Tip: All admin changes are automatically committed to GitLab, ensuring consistency across all users and environments.

Comment Deletion Policy

Understanding the three deletion methods

Method 1: Individual Comment Deletion

Who can use: Any user viewing the report

Hover over any comment to reveal the Delete button
Click Delete to remove that specific comment
Confirm the deletion in the popup dialog
Scope: Deletes only the selected comment
Permissions: No password required

Method 2: Mark All as Resolved (Ctrl+D)

Who can use: Users with admin password

Press Ctrl+D from any report page
Enter admin password to confirm
Scope: Marks ALL comments in the current report as resolved
Effect: Comments are hidden but not permanently deleted
Use case: When comments are addressed and should be archived

Method 3: Bulk Comment Deletion (Admin Only)

Who can use: Users with admin password

Press Ctrl+A to open Admin Modal
Select Option 3: Remove All Comments
Enter admin password to confirm
Scope: Permanently deletes ALL comments from the current report
Use case: When you need to completely clean up and start fresh

Critical Information:

Method 1 & 3: Deletion is permanent and irreversible
Method 2: Comments are marked as resolved (can be restored if needed)
Changes are immediately committed to GitLab when using "Save & Publish"
Use bulk operations with caution - they affect all report viewers
Admin password required for Methods 2 and 3 - contact administrator for access

When to Run a New Pipeline

Understanding when manual pipeline runs are needed

Scheduled Automatic Runs

Pipelines run automatically in these scenarios:

Weekly Schedule: Every Monday at 6:00 AM (configurable)
After Code Changes: When test results or metrics are updated

When to Manually Run Pipeline

Trigger a manual pipeline run when:

Modified JIRA Queries: After changing queries in Admin Modal → JIRA Queries Editor
Need Fresh Data: When you need updated metrics outside the weekly schedule
After Major Changes: Following significant test execution or code updates
Verification: To verify that query changes produce expected results
Emergency Updates: When stakeholders need immediate report updates

How to Run Pipeline Manually

Open Admin Modal (⚙️ icon → enter password)
Select "Option 4: Run Pipeline"
Click "🚀 Start Pipeline" button
Monitor progress in the console (shows each stage)
Wait for completion (typically 5-10 minutes)
New reports are automatically deployed to GitLab Pages

Pipeline Efficiency: Running the pipeline generates ALL reports at once (Automation, Manual, Security, Quality, Performance, Static Code Analysis), ensuring consistency across all testing disciplines.

Troubleshooting & FAQ

Common issues and solutions

Common Issues

Q: My comments disappeared after refreshing the page

A: You likely used "Save" instead of "Save & Publish". Use "Save & Publish" to commit changes to GitLab.

Q: Modified JIRA queries don't show new data

A: You need to run a new pipeline after modifying queries. Go to Admin Modal → Run Pipeline.

Q: Can't access Admin Modal

A: Press Ctrl+A and enter the correct admin password. Contact your project administrator if you need access credentials.

Q: Pipeline fails to start

A: Check your network connection and ensure you have proper GitLab access permissions. The fallback simulation will run if GitLab API is unavailable.

Q: Charts or data not displaying

A: Try refreshing the page. If the issue persists, check browser console for errors or run a new pipeline to regenerate data.

Need Help? Contact the PSO team or your project administrator for additional support and troubleshooting assistance.