How to compile Cypress TypeScript without running tests

Question

Our project uses Cypress to run e2e tests. We have 5 different suites that run twice a day, at different times.

My problem is that we can currently introduce compilation problems and we won't find out until we run the e2e tests, which is after we've committed. I would like to be able to build my Cypress TypeScript to make sure it doesn't have any type errors so that we can prevent pushing to main.

I have not been able to find some configuration that would compile all the TypeScript but would not run the tests. Has anyone been able to achieve such configuration?

Cant you compile TS regularly? Why you need cypress to do it? If missing some global variables just install the Cypress types — Raz Luvaton
– Raz Luvaton, Commented Sep 21, 2021 at 17:29
@RazLuvaton We use cucumber and my (unfounded) concern was that Cypress converts the feature files into JavaScript and I thought I would not be compiling the full code. You are correct though, that I don't need to compile the generated code from cucumber feature files. — Ruan Mendes
– Ruan Mendes, Commented Sep 24, 2021 at 13:40

Ruan Mendes · Accepted Answer · 2021-09-24 13:38:32Z

1

It turns out to be as simple as @RazLuvaton mentioned. Just run tsc on your own. You can even pass the --no-emit if, like me, you just want check types.

answered Sep 24, 2021 at 13:38

Ruan Mendes

92.7k31 gold badges161 silver badges225 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How to compile Cypress TypeScript without running tests

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related