How juanpa90cap/ci-test works
Project type and purpose
• This is a single‐page React frontend application (“Pokedex”) that fetches data from a public Pokémon REST API.
• It is set up with a full CI/CD pipeline (GitHub Actions), unit tests (Jest), end-to-end tests (Cypress), linting (ESLint), and a Webpack‐based build + production serve setup.
File structure
• Top level: configuration files (.babelrc, .eslintrc.js, webpack.config.js), CI workflows (.github/workflows), package.json scripts.
• “src/”: React components and custom hook (useApi.js).
• “public/”: static index.html.
• “test/”: Jest unit tests for components.
• “cypress/” and “ci-test/”: Cypress e2e tests + configs.
• app.js: entry point for production server.
README for additional insights
• Key commands: start dev server, run tests, lint, build, start production.
• Emphasis on CI/CD pipeline badge and exercises for the Full Stack open course.
• No backend service in this code base; external API is the PokeAPI.
Elements
• Blue for developer/build artifacts
• Green for CI/CD stages
• Orange for runtime/third-party services
Detail level
• CI stage as its own node (Install & Lint → Unit Tests → E2E Tests → Build → Deploy).