Noam3kCH / answers-fed-entry-level-exam

Wix Answers FED Entry Level Exam

Hi there!
In this exam you will extend and add new features to a simplified ticketing system. It aims to provide you a glimpse of our day-to-day work, along with some connection to our domain (helpdesk & ticketing system). The task's main purpose is to test your ability to learn new topics and deliver high quality digital products. It combines building UI components and a touch of server development as well.

While no previous background is required to complete this task or to apply to this position, we do recommend getting to a basic level on the following subjects:

• Git
• JavaScript
• HTML & CSS
• React
• Node.js

Getting Started

1. Make sure you have an GitHub account
2. Go here and import this repository into your account. Make sure to select the private option
3. Clone your new repository to your computer
4. Make sure you have Node.js 10 or higher and npm 6 or higher installed
5. Install the project dependencies by running npm install from the project's directory (using a terminal)
6. Run the project by running npm start

You should now have the development version running on your computer and accessible via http://localhost:3001

Tasks

The exam is split into 3 parts. The first part is about adding UI functionality. The second part goes a bit broader into the client-server integration and business logic. The third part is about creativity and good "big-picture" intuition. We also have a 4th part that is only expected from those with previous commercial experience.

After each completed step, please commit and push. The commit message should be something like Part 1a - show content, Part 2b - search filters.

Part 1 - Ticket item improvements

a. Our tickets list is only showing the title. Make it show the content as well, as following:

Friendly reminder to commit and push after completing this step.

b. Some agents can't answer all tickets, and want an option to hide some. Add a hide button that will hide the tickets from view. Make sure there is an option to restore it as well:
Friendly reminder to commit and push after completing this step.

c. Our ticket's data might also contain labels (tags), but we're not making use of them in our UI. Fix that by adding the labels according to the following design below. PS: feel free to add more labels to the data (data.json) if you need.
Friendly reminder to commit and push after completing this step.

d. Step a wasn't enough - some tickets have long content. Add a show more / show less functionality when the content exceeds 3 lines, as following:

Friendly reminder to commit and push after completing this step.

Part 2 - List functionality

a. Agents are complaining that our search functionality isn't working properly. They gave the example that when searching for "wix stores", the ticket titled "Search bar for my wix store" (id 6860d043-f551-58c8-84d6-f9e6a8cb0cb2) is not returned. Checking the data, that ticket does exist.. Find the issue and fix it.
Friendly reminder to commit and push after completing this step.

b. There is a need to find tickets before/after a certain date, and our designer is on vacation to design proper UI for it. Change the search functionality so that when searching for after:27/09/2019 api, only tickets matching the word "api" created after 27/09/2019 will show. Add support for before:[DATE] and from:[EMAIL] as well.
Friendly reminder to commit and push after completing this step.

c. We're showing only 20 tickets but agents can swear there are more. Solve this problem. Keep it mind the number of tickets is planned to grow exponentially very soon so make sure to think of a proper solution.
Friendly reminder to commit and push after completing this step.

Part 3 - Your extra touch

Think of a small addition to this project and make it happen. If you need inspiration, you can check out our real ticketing app at https://wix.com/wixanswers and grab some ideas from there ;) It should involve adding something to the UI, or server (or both!). A good rule of thumb for the effort here is that it should not exceed the time that took you to perform Part 2.

Note: this is step is also mandatory.
Friendly reminder to commit and push after completing this part.

Part 4 - [Previous experience only] Automated testing

If you do not have previous experience in web development, you can skip this part. Otherwise, it is mandatory.

a. Add at least 3 automated tests browser using puppeteer, testing key features of your choice. b. Add component tests (using jest) to your work from part 1.

General notes

• Test your work well. Think of edge cases. Think of how users will use it, and make sure your work is of high quality
• If you have any questions regarding the task itself or its environment, feel free to ask in the exam's e-mail. For general coding / technology questions, please consult stack overflow, forums and other sources of your choice.

Submitting

1. add [e-mail], [e-mail], [e-mail] & [e-mail] as collaborators to your imported repo.
2. send the repo's URL back to the email you got from us.