dotenv VS CodeceptJS

We will put our Emailjs environment variables in a dotenv (.env) file. To read more about the purpose of this file click here.

Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.

dotenv: Designed to load environment variables from a .env file into the process.env environment

Like Doppler, Infisical uses environment variable injection. Similar to the Dotenv package for Node, when used in Node, it injects them at run time into the process object of the running app so they're not readable by any other processes or users. They can still be revealed by a crash dump or logging, so that is a caveat to consider in your code and build scripts.

We'll be working with databases' ids and different info that should be secured so I would advise you to create a .env file to store said info. We'll do this by installing dotenv into our project and use it accordingly:

dotenv - For reading our API keys from the environment

As an avid dotenv user I wanted to thank their maintainers for keeping the project alive for 10 years (wow). A perfect exemplary of dedication to Open Source.

Sensitive data like database URLs, API keys, and passwords should never be hardcoded in your application code. Instead, use environment variables accessed at runtime to keep this information secret. Popular dotenv libraries like dotenv make this easy for Node.js apps.

But honestly, it may be preferable for you to use a single framework that does support both technologies (Web and Mobile) out of the box like webdriver.io or codecept.

Extending my screenshot tests, I discovered the useful configuration option to set fullPageScreenshots: true. When I wanted to set different window sizes, I was not the first one struggling to resize the browser window in CodeceptJS programmatically.

CodeceptJS – A wrapper for different tools in one interface. Language: JavaScript/TypeScript. Frameworks that are wrapped: Playwright, Webdriver.io, Puppeteer, Protractor, etc. The service also comes with a large community and is easy to install and use for e2e testing.

I'm saddened codeceptJS wasn't even mentioned. It's easily better than most of the ones listed except Cypress.

back when I was doing FE, I found https://codecept.io, which is the same concept as Cypress but with a Playwright driver. Have not used but thought it's worth a mention

There are enough blog posts about Jest or Cypress already, so let me introduce Codecept. It comes in two flavors. There is Codeception for PHP, and there is CodeceptJS for JavaScript which we will be using here.

No mention of Codecept.js?

This is where https://testomat.io comes in. I discovered this TCM whilst working with https://codecept.io/ and part of their Slack group. Testomatio is built by the team behind codeceptjs, bringing in vast experience in test automation behind the scenes.

I think you should add codeceptjs which does API testing on top of selenium / puppeteer tests.

Maybe take a look at https://codecept.io/