Configurando el entorno de pruebas para nuestro proyecto

How to modularize applications for development and test environments?

When creating complex applications, one of the fundamental skills is to be able to modularize them properly to ensure that testing is performed effectively in an environment that closely simulates production. This process ensures that any changes to the code can be tested before being deployed. Let's explore how to do this step by step.

What aspects to consider for separating responsibilities?

Separating responsibilities is a good practice in software development that helps keep the code clean and manageable. It also allows the application to run in both normal development and test environments.

1. Setup: This is the stage where all the application configuration such as routers, middlewares and security settings are set up.
2. Listening: This is the part where the application starts receiving requests on a specific port.

To implement this separation, it is common to create a dedicated file containing the function in charge of setup.

// In app.jsfunction createApp() { const app = express(); app.use(cors()); // Router and middleware setup return app;}module.exports = createApp;

How do we structure the main application for production and testing?

Once the responsibilities are separated, the main application can import this configuration and decide whether it will run in a development or test environment. In a file like index.js, you simply import the function and create its context:

// In index.jsconst createApp = require('./app');const app = createApp();const PORT =process.env.PORT || 9000;
app.listen(PORT, () => { console.log(`Serverrunning on port ${PORT}`);});

How to create test endpoints in a real application?

To validate that our tests are effective, it is important to have test endpoints. If they do not exist, they must be created, following the architecture in which the production application was released.

1. Define the endpoint: You can define a simple endpoint such as /hello and specify the response it should generate.

// Example of endpoint creationapp.get('/hello', (req, res) => { res.status(200).json({ name: "Nico" }); });

2. Test the endpoint: Use tools like Postman or Insomnia to verify that the endpoint responds correctly with the expected name and status.

What will you learn in the next sessions?

Now that you've learned how to tune the architecture for testing, the next step is to track test coverage. I will guide you on how to set up reports to measure what is the percentage of test coverage on our endpoints. Let's move forward together towards the E2E testing domain!