-
Notifications
You must be signed in to change notification settings - Fork 0
Resources & Tools
This page is the central hub for all essential links, tools, and systems used by the QE team.
These are the environments where you will test and validate features.
| Environment | URL | Purpose | Notes |
|---|---|---|---|
| Dev | [Development] | Used by developers for initial testing | No certifications applied needed |
| Staging | [EC2] | Pre-production environment | Used for release validation |
| Production | [Production] | Live system | Certifications applied might be needed |
The application integrates with Cosmic Latte external service, a third-party service provider embedded into the application.
- Service URL: Comic Late environment
- Credentials: Registration process should be completed and Technical lead should grant access to obtain verification code
🔑 Access & Credentials
- Access is managed via: [360 ID for Production and EC2 and via registration for Development environment]
- Credentials should never be shared publicly
QE Responsibilities
- Validate correct integration with Cosmic Latte
- Verify environment-specific configurations
- Test error handling and fallback scenarios
- Confirm data consistency between systems
These tools are used to track work, bugs, and sprint progress.
- Board: Miro board
- Sprint Board: GitHub Project Board
📌 Usage
- Track user stories and bugs
- Update ticket status
- Add comments and evidences during ticket testing
Figma is used as the source of truth for UI/UX designs and mockups.
- Prototypes: Figma link
📌 How QE Uses Figma
- Validate UI against designs
- Check spacing, alignment, and visual consistency
- Review expected behaviors (hover states, transitions, etc.)
- Clarify requirements when acceptance criteria are unclear
- Always compare implemented UI with the latest design version
- Confirm with Product/Design if discrepancies are found
- Pay attention to responsive behavior (if defined)
This is where test cases are created, maintained, and executed.
Tool: Test Link
📌 When to Use
- Create new test cases
- Update existing ones
- Execute test cycles for build versions
- Prepare and execute Regression tesitng
Used for backend validation and integration testing.
Swagger / API Docs: Swagger Postman Collection: Internal Documentation:
📌 When to Use
- Validate API responses for backend tickets
- Test edge cases
- Understand request/response structure
Access to repositories and version control.
- Main Repository: [JU-DEV-Bootcamps/ERAS] https://github.com/JU-DEV-Bootcamps/ERAS
- Front End Repository: JU-DEV-Bootcamps/ERAS-FE
- Backend Repository: JU-DEV-Bootcamps/ERAS-BE
Tools used for builds, deployments, and pipelines.
CI/CD Tool: GitHub Actions
📌 QE Responsibilities
- Monitor deployments
- Validate successful builds
- Perform smoke testing after deployment
- Monitoring & Logs (Optional but Recommended)
- Missing permissions → Contact [team/channel]
- Expired credentials → Reset via [system]
- ✅ Keep this page updated when tools or URLs change
- ✅ Do not share sensitive credentials in the wiki
- ✅ Validate access during your first days
💡 If you notice missing or outdated links, please update this page or notify the owner.