DevOps for Klavis' CI/CD Pipeline and Automated Testing

# GitLab CI/CD Pipeline + Integration & E2E Tests Implementation for Klavis

## Project Overview

**Company**: Klavis (klavis.app / klavis.be)
**Duration**: 7 days (tight schedule)
**Budget**: $500 - $800 USD (fixed price, negotiable based on experience)
**Experience Level**: Intermediate to Expert

## About the Project

We need an experienced DevOps/QA engineer/team to implement a complete CI/CD pipeline with automated testing for our staging application. The schedule is tight, so we're looking for someone who can work efficiently and deliver quickly with minimal back-and-forth.

## Technical Stack

**Backend:**
- .NET Core API
- GitLab repository
- PostgreSQL database

**Frontend:**
- Vue.js / Vite
- npm
- GitLab repository (separate from backend)
- Consumes the .NET Core API

## Scope of Work

### 1. Backend Repository CI/CD Implementation

**Required Deliverables:**
- Complete `.gitlab-ci.yml` configuration with stages: build, test
- Docker service configuration for PostgreSQL test database (?)
- GitLab pipeline setup with proper caching and artifacts
- Protected branch rules and merge request settings documentation > target: [given branch name]

**Integration Tests to Implement (around 5 test cases):**
- API endpoint testing (GET, POST, PUT, DELETE)
- Authentication/authorization flows
- Business logic validation
- Error handling and edge cases

### 2. Frontend Repository CI/CD Implementation

**Required Deliverables:**
- Complete `.gitlab-ci.yml` configuration for Vue.js/Vite application
- Unit test setup and configuration
- Build optimization and artifact generation
- Deployment pipeline for staging (and production?) environment > target: [given branch name]
- Integration with backend API for E2E tests (?)

**E2E Tests to Implement (around 5 test scenarios):**
- User authentication flows
- Critical user journeys (main features of the app)
- API integration validation
- Form submissions and data persistence
- Navigation and routing tests

### 3. Documentation & Knowledge Transfer

- Clear README documentation for both repositories explaining:
- How to run tests locally
- How the CI/CD pipeline works
- How to add new tests
- Troubleshooting common issues
- 1-hour video call for knowledge transfer and Q&A

## Requirements

### Must Have:
- **Proven experience** with GitLab CI/CD (please share examples)
- **Strong background** in .NET Core testing (xUnit, WebApplicationFactory)
- **Experience** with Vue.js/Vite and E2E testing (Playwright or Cypress)
- **Fast turnaround** - ability to work efficiently under tight deadlines
- **Self-sufficient** - minimal hand-holding required, ask smart questions
- **Excellent communication** - daily progress updates via GitLab issues/comments
- Available to start **immediately**

### Nice to Have:
- Experience with similar full-stack applications
- Knowledge of test-driven development (TDD)
- Experience with Docker and containerization
- Background in DevOps best practices
- Familiarity with Klavis or similar platforms

## Project Timeline

**Day 1 - 5**
- Days 1-2: Backend CI/CD + integration tests setup
- Days 3-4: Frontend CI/CD + E2E tests setup
- Day 5: Testing, debugging, refinement
Validation, Integration by the team

**Days 6 -7:**
- Days 6: Documentation and knowledge transfer
- Day 7: Buffer for fixes and final adjustments

**Total**: Maximum 10 business days

## Next
- Writing all integration and e2e tests


## How to Apply

Please include in your proposal:

1. **Relevant Experience**: Links to similar CI/CD pipelines you've implemented (GitLab specifically)
2. **Testing Portfolio**: Examples of integration/E2E test suites you've written
3. **Availability**: Confirm you can start immediately and commit to the timeline
4. **Approach**: Brief outline (3-5 bullets) of how you would tackle this project
5. **Questions**: Any clarifications needed about the stack or requirements
6. **Estimated Timeline**: Your realistic assessment of completion time

**Red flags - applications will be rejected if:**
- Generic copy-paste proposals
- No specific GitLab CI/CD experience mentioned
- Requesting extensive preliminary meetings before starting
- Timeline longer than 7 days
- No testing examples provided

## Payment Terms

- 40% upon completion of backend CI/CD + tests (milestone 1)
- 30% upon completion of frontend CI/CD + tests + documentation (milestone 2)
- 30% upon documentation delivery and knowledge transfer

## Additional Information

- **Access**: You'll be given developer access to both GitLab repositories
- **Communication**: Primary communication via Freelancer + GitLab (issues, merge requests, comments)
- **Testing Environment**: Staging environment URLs will be provided
- **Code Review**: All merge requests will be reviewed before merging to main
- **Working Hours**: Flexible, but must be available for at least one synchronous call for kickoff and one for handoff

## Why Work With Us?

- Clear, well-defined scope
- Professional development environment
- Opportunity to work on a live production application
- Potential for ongoing work if collaboration goes well
- Fast decision-making and payment processing

---

**To apply**: Submit your proposal with all required information. We'll review applications within 24 hours and schedule interviews with shortlisted candidates immediately.

We're looking for quality over quantity - a well-thought-out proposal from the right person will be prioritized over quick generic responses.

**Questions?** Feel free to ask in your proposal, but please read this description carefully first.

Looking forward to working with a talented professional/team that can deliver this efficiently!