How alexyirsa/it-cert-automation-practice works
Main Components
• Repository Metadata and Configuration
• “docs” (with contributing.md) and other general files like LICENSE and README.md.
• Course-Specific Modules
• Within each course block, further subdivide into the labs (e.g., Course3 → Lab4; Course4 → Lab4; Course5 → Lab3). Each lab block should include annotations on what type of files they contain.
• Lab-Level Artifacts
• For example, in Course3/Lab4, list “validations.py” as a Python script likely focusing on input or data validations.
• In Course4/Lab4, note the “employees-with-date.csv,” indicating data input for employee records that might be used to test automation or processing steps.
• In Course5/Lab3, include “hello_cloud.py” as a Python script and “hello_cloud.service” which could be a configuration or service file, hinting at a simple cloud service integration or simulation.
Relationships and Interactions
• The overall repository is the container that houses these separate modules, meaning that while the courses are self-contained, they represent parallel exercises using the same underlying ideas.
• That CI/CD components in the .github directory operate on the entire repository (e.g., automated checks on pull requests across courses).
Architectural Patterns & Design Principles
• Modularity: Each course folder is effectively an independent module that encapsulates its own labs, assets, and sometimes dependencies.
• Separation of concerns: Drawing boundaries between repository management/configuration files (GitHub workflows, docs) and course-specific materials.
• The design is lightweight and educational in purpose – a learning scaffold rather than a production application.