Scribd
Upload
35 views3 pages

Teste Frontend Manager Systems - EN

The document describes a test to build a simple single page application with login and country management features. It provides backend API documentation and initial user/country data. The tasks are to create a login screen, main screen with user menu and country list, and country editing functionality while handling token expiration transparently.

Uploaded by

htzhfkscz7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
35 views3 pages

Teste Frontend Manager Systems - EN

The document describes a test to build a simple single page application with login and country management features. It provides backend API documentation and initial user/country data. The tasks are to create a login screen, main screen with user menu and country list, and country editing functionality while handling token expiration transparently.

Uploaded by

htzhfkscz7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Introduction

This test is composed by the construction of a simple SPA, composed by a screen


used to register countries

The test can be developed in any framework, as long as it do everything specified


on the test

To compose the whole SPA, a ​backend ​in Spring Boot was developed and it is
available on the link ​https://owncloud.mngs.com.br/index.php/s/9wnUxvxe6rTavEU

To run it, you must have Java installed on the computer and execute
the .jar :

• ​Double click on the .jar (it won’t open anything, only run in the background), or;
• ​java -jar BackendTesteFrontend-1.0.0.jar​ on the command
line.

Once running, the backend will listen on the localhost doot 8090. The API is
available on the address ​http://localhost:8090/swagger-ui.html

All the API methods need a user authentication token to be sent as parameter. The
token can be obtained trough the endpoint /usuario/*.

The token has a expiration time of 5 minutes and can be renewed on the endpoint
/usuario/*. If a invalid/expired token is passed to the methods, the API return a
HTTP 401 as answer.

Initial Data

There are already two users


registered:
Login Password Permission

convidado manager User

admin suporte Admin

There are 3 countries registered too.

What should you


develop

1. Login screen, with login and password


2. The login and password authentication must be on the ​backend
3. Should save the token on the local storage of the browser, with the info of the
user (if it is a normal user or admin, the info comes with the auth answer)
4. Main screen with simple top menu that has a option “paises” (“countries” in
portuguese). On the superior part of the screen the name of the user must be
presented (comes with the answer)
5. Screen to see and edit countries
1. Only admin can edit/include/delete
2. Must exhibit the countries list, with the pagination and data ordenation
on the client side
3. Must permit to edit/include/delete countries
4. The form fields must have data validation adequate to the data
(Example: the “Estado” must be only two characters , like “SP”, “SC”,
“MA”, etc.)
5. Because the token expires, it should be automatically renewed before
every requisition or capture the 401 from the backend and reauthorise
automatically (this process should be transparent to the user, the user
cant know that this is happening)

Result presentation

The code must be committed to a private github repo, shared with the user
“mngsgoncalves”

Test result

The result evaluation will consider:

1. Developing what was asked


2. Clean and documented code
3. Attention to the data validation and
process
4. Interface usability

You might also like