dominique-mueller / no-skipped-tests

Analyzes your project for focused or ignored tests

Hi, I am a Web Developer based in Frankfurt am Main (Germany), passionate about developing visually appealing, user friendly and accessible websites and web applications, libraries and design systems.

I work a lot with:

• 📐 Markup (HTML, JSX) · Styling (CSS, SASS, JSS, Tailwind) · Programing Languages (JavaScript, TypeScript)
• 🌟 React & Next.js · Angular · Vue.js & Nuxt
• 🔨 Unit & Integration Testing (Jest, Jasmine) · End-to-End Testing (Cypress, Playwright, Puppeteer)
• ❤️ User Experience (Usability, Visual Design, Accessibility, Performance)
• 🔧 Version Control (Git, Git Flow) · CI / CD (GitHub Actions, GitLab) · Code Quality (ESLint, Prettier)
• 📎 Technical Documentation · SCRUM & Kanban

no-skipped-tests's Issues

🐞 Installation instructions out of date?

After following the installation instructions from the README, npm run pretest fails;

$ npm list no-skipped-tests
[email protected] ~/projects/my-project
└── [email protected]

$ npm run pretest

> [email protected] pretest ~/projects/my-project
> no-skipped-tests

sh: no-skipped-tests: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] pretest: `no-skipped-tests`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] pretest script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     ~/.npm/_logs/2019-05-06T02_17_06_493Z-debug.log