The purpose of this exercise is to build a small application, based on a fictional use case, but related to the daily job at Wazuh.
Pay attention to details like documentation and testing. We want to ensure our future colleagues can deliver quality code and documentation.
We want you to:
- Document the architecture and features of your work.
- Document the steps to run the tests within the provided development environment.
Please tell us if you have any problems/challenges during the development of the task and how you solved them. Also, we expect you to suggest features that could be interesting according to the requirements and the provided context.
We expect our candidates to be able to work with:
- NodeJS
- ReactJS
- A testing framework (preferably Jest)
- Docker
We expect knowledge as a user of virtual machines like Virtualbox, Hyper-V, KVM, etc.
Information security professionals use Wazuh to analyze the security status of all elements of their infrastructure.
These processes are often performed within the framework of one of the security standards, such as PCI DSS, ISO 27001, SOX, etc. One of the needs that these professionals have is to make lists of tasks related to these processes.
These users would like to be able to know:
- the tasks they have already done.
- the tasks they have left to do.
- when they have completed a task, or when they plan to execute it.
They would also like to be able to search for tasks, for example by the text they contain, or by a list of tags. Each task can be in different states, such as planned, successfully executed, or executed with error.
As a full stack developer, you have been tasked to implement such an application on the platform on which Wazuh is integrated.
The application must be a plugin for OpenSearch Dashboards and persist the data in an OpenSearch index.
The user must be able to:
- read and render the TO-DO items.
- create new TO-DO items and persist them (in an OpenSearch index).
- set TO-DO items as completed.
- delete TO-DO items.
- search TO-DO items.
- visualize the TO-DO items using dashboards, such as tables and charts.
The application architecture must have (at least):
- frontend.
- backend for frontend.
- tests.
Use ReactJS for the front-end.
The OpenSearch Dashboards provides a library of UI components (@opensearch-project/oui)
that can be used to create new functionalities and keep the UI appearance. This library
is referenced in the source code as @elastic/eui. You can create the user interface
of the application with other libraries you know, but using the provided UI library will
be positively valued.
At least, a table and a chart must be created, but add any other visualization you consider. We are interested in seeing how you would represent the data to maximize the value provided to the user.
Including additional functionalities to ease the navigation, such as sorting or pagination, will be very positively valued.
Write a small backend for the application in NodeJS which implements a REST API. This server-side code of the app for OpenSearch Dashboards will contain the logic of the application related to the resources, in this case, the TO-DO items. Use the services provided by the platform to interact with the index (database).
Check the References for additional documentation.
The application must have some tests related to UI components and functionalities. The
preferred library is Jest, as it's the one OpenSearch Dashboards and Wazuh use, but you
are free to use any other testing library.
Jest is already configured, so you can focus on writing the tests. If you decide to use a different testing library, its configuration is on your side. In this case, provide instructions about how to run the tests. If the challenge does not include working and passing tests or if we cannot manage to verify that, the challenge will be void.
The tests are intended to be executed within the Docker container.
The TO-DO items must, at least, have a title and a status. Add any other properties you consider interesting to enrich the challenge. Think about what information you want to display and the best way to visualize it, and add as many properties as you need, for example:
- Creation date.
- Completion date.
- Assignee.
- ...
We already provide you with a development environment based on Docker. Continue reading its README.md to get started.
- OpenSearch Documentation
- Introduction to OpenSearch Dashboards Plugins
- UI components library documentation - @elastic/eui
- Jest
OpenSearch forked @elastic/eui as @opensearch-project/oui, but they do not hold any documentation yet, hence we use the Elastic UI documentation instead. Be aware that there might be differences between these 2 libraries.