How fimyh/automatisation-formation works
Project type and purpose
• Key clues: presence of Robot Framework test files (*.robot under resources/ and tests/), Python scripts (read_incident.py, test_selenium.py), a Jenkinsfile and docker-compose.yml, plus Chromedriver.exe.
• Purpose: run end-to-end tests (UI via Selenium, incident-based tests against ServiceNow and JIRA), generate reports (report.html, log.html, output.xml), and upload incident results back to JIRA.
File structure
Top-level artifacts:
• Jenkinsfile – defines CI/CD pipeline.
• docker-compose.yml – defines containers for tests or dependencies.
• requirements.txt & package.json – Python and Node/JS dependencies, suggesting some tooling or reporters rely on npm.
• chromedriver.exe – local Selenium WebDriver.
• incident.json – sample payload for incident-based tests.
• Python modules in libraries/ – custom keywords (JiraUpload.py, shadow.py).
• resources/ – Robot Framework keyword definitions and variables.
• test.robot, tests/*.robot – actual Robot Framework test suites.
• test_selenium.py – standalone Selenium test.
README
• README only contains a title (“ProjetAlten”), so we assume that most architectural insights must come from the structure itself.
Main components and interactions
a. CI/CD layer (Jenkins)
• Orchestrates the pipeline: checks out code, spins up containers via Docker Compose, installs dependencies, runs tests, collects artifacts, and optionally uploads results to JIRA.
b. Container/Environment setup (Docker Compose)
• Defines the test environment (e.g., a container for Python, optional mock servers, perhaps ServiceNow mocks).
• Ensures chromedriver and browsers are available.
c. Test Engine
• Robot Framework core that glues together:
– resources/ (keyword libraries and variable files)
– tests/*.robot and test.robot (test suites)
– custom Python libraries (libraries/JiraUpload.py for pushing to JIRA; shadow.py for any utilities)
• test_selenium.py runs Python‐only Selenium tests.
d. External Services
• ServiceNow (real or sandbox) – accessed via keywords in resources/servicenow_keywords.robot
• JIRA – accessed via keywords in resources/jira_keywords.robot and the JiraUpload.py library
e. Reporting & Artifacts
• Robot generates output.xml, log.html, report.html
• test_selenium.py may produce its own logs
• Jenkins archives these artifacts and can push statuses to JIRA
Architectural patterns & design principles
– Separation of concerns:
• CI/CD layer (Jenkinsfile) is isolated from test logic
• Environment definition (docker-compose.yml) decoupled from code
• Test code separated into reusable resource keyword files and test suites
– Extensibility: adding a new external system just requires a new resource keyword file and library
– Reusability: custom Python libraries under libraries/ are loaded by Robot to share functionality
– Label every component clearly