Backend Programmer Test
Uploaded by
ScribdTranslationsBackend Programmer Test
Uploaded by
ScribdTranslationsBackend Developer Test
Objective:
Evaluate the candidate's knowledge and skills for web application development.
Backend level.
Programming Language: Knowledge of an appropriate programming language for the
Backend construction of the web application. Options: Java, CSharp, PHP
Database: Knowledge of SQL Language. Knowledge of a database management system and
its particularities: Programming language of Triggers, Stored Procedures.
Opciones: PostgreSQL, SQL Server, MySQL Server
SOLID Programming Principles: Knowledge and applications of programming principles
SOLID, as well as the main programming patterns.
Tasks to be Done
1. Create a web service that allows authorized users to manage their tasks:
Consult, Create, Modify, Delete. (See Available Web Services and Graphical Interface)
2. Create unit tests to verify the correct functioning of the methods.
offered by the service
3. Document the service using a tool like Swagger.
4. Publish the code in a GitHub repository. For review and evaluation.
Scope:
It should be included:
User Authentication and Authorization Mechanism.
User management (consult, create, update, delete)
Data persistence (tasks) in a SQL type database.
Métodos que debe publicar el servicio: Consultar, Crear, Actualizar, Borrar Tareas.
The following information related to the tasks must be stored at a minimum:
users
Creation Date
Description
Completed (yes/no)
Expiration Date
Task Author (User who created the task)
Description Web Services Methods
Consult Tasks
HTTP Method: GET
/tasks/consult
Parameters: Those necessary for the user to be able to consult the scheduled tasks by
various criteria:
Consult all tasks (including those of other users)
Consult only my tasks (those of the authenticated user)
Consult only completed tasks, only those that are pending, or all regardless of their status.
completion status.
Sort the query by due date.
Combine the previous ones.
List of Tasks that meet the conditions established in the parameters.
Prerequisite: authenticated user
Create Task
POST
/tasks/create
Parameters: it must ask for the necessary parameters to store information about the task.
that the user is creating.
the created task is returned.
Prerequisite: authenticated user
Task Update
Method: POST
/tasks/update
Parameters: it must be able to receive an object with the information that the user wants to update
in a task:
// mandatory
Description optional
expiration date optional
Yes //optional
Response: the updated task is returned
Prerequisite: authenticated user, authorized user (only the user who created the task)
can update
Delete from Task
POST
/tasks/delete
Parameters: it must receive information that allows it to uniquely identify the task that the
user wants to delete.
The service does not return a response.
Prerequisite: authenticated user, authorized user (only the user who created the task)
can update
