evernote-ci-integration

# Evernote CI Integration ## Overview Configure continuous integration pipelines for Evernote integrations with mock-based unit tests, sandbox-based integration tests, credential management, and deployment workflows. ## Prerequisites - Git repository with Evernote integration code - CI/CD platform (GitHub Actions, GitLab CI, etc.) - Test framework (Jest, Vitest, or Mocha) - Sandbox API credentials for integration tests ## Instructions ### Step 1: GitHub Actions Workflow Create a workflow that runs unit tests on every PR and integration tests on merges to main. Store sandbox credentials as GitHub Actions secrets. ```yaml # .github/workflows/evernote-ci.yml name: Evernote CI on: [push, pull_request] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: { node-version: '20' } - run: npm ci - run: npm test - name: Integration tests if: github.ref == 'refs/heads/main' env: EVERNOTE_DEV_TOKEN: ${{ secrets.EVERNOTE_SANDBOX_TOKEN }} EVERNOTE_SANDBOX: 'true' run: npm run test:integration ``` ### Step 2: Mock Evernote Client for Unit Tests Create a mock NoteStore that returns predictable data without hitting the API. Mock `createNote`, `getNote`, `findNotesMetadata`, `listNotebooks`, and `listTags`. ```javascript class MockNoteStore { constructor() { this.notes = new Map(); this.notebooks = [{ guid: 'nb-1', name: 'Default', d...