Workle's test assignment for the position of Junior Frontend Developer

Test task for Workle

The task

  1. Make up the page according to the layout .
  2. Add functionality:
  • Take data through the API of the Unsplash.com website .
  • When you click on the author, his profile opens in a separate tab.
  • When you click on a photo, nothing happens.

Tools

To perform this task, you must use the Vue.js framework

Structure

public
├─── favicon.ico
└─── index.html
src
├─── App.vue
├─── main.js
├─── assets
│ ├─── fonts
│ │ ├─── fonts.css
│ │ ├─── RobotoCondensed-Bold.svg
│ │ ├─── RobotoCondensed-Bold.ttf
│ │ ├─── RobotoCondensed-Bold.woff
│ │ ├─── RobotoCondensed-Regular.svg
│ │ ├─── RobotoCondensed-Regular.ttf
│ │ └─── RobotoCondensed-Regular.woff
│ └─── img
│ ├─── eye.svg
│ └─── loading.png
└─── components
     ├─── Error
     │ └─── Error.vue
     ├─── Loading
     │ └─── Loading.vue
     ├─── Pagenation
     │ └─── Pagenation.vue
     └─── Post
          ├─── Autor.vue
          ├─── Post.vue
          └─── Views.vue

Supplements

To improve the ergonomics of the interface, the following functions were added that were not included in the main task and can be disabled if desired:

  • Loading wheel - displays that at the moment the system is not frozen, but an internal action is taking place.

  • Error message - displays that an error occurred while executing the task and the user is given the opportunity to repeat the action.

In order to disable this or that addition in the App.vue file, you must set the values ​​of showLoadingWheel or showUserErrorMessage to false.

Note : if you disable the display of the error for the user, the error is displayed in the console.

Screenshots of the completed task

1000+

768+

480+

320+

Additional tools

To achieve the final result, the following tools were also used:

Download Details:

Author: 6eremotuk01

Source Code: https://github.com/6eremotuk01/workle-test-task

#vuejs #vue #javascript

What is GEEK

Buddha Community

Workle's test assignment for the position of Junior Frontend Developer

Hire Frontend Developers

Create a new web app or revamp your existing website?

Every existing website or a web application that we see with an interactive and user-friendly interface are from Front-End developers who ensure that all visual effects come into existence. Hence, to build a visually appealing web app front-end development is required.

At HourlyDeveloper.io, you can Hire FrontEnd Developers as we have been actively working on new frontend development as well as frontend re-engineering projects from older technologies to newer.

Consult with experts: https://bit.ly/2YLhmFZ

#hire frontend developers #frontend developers #frontend development company #frontend development services #frontend development #frontend

Fredy  Larson

Fredy Larson

1595059664

How long does it take to develop/build an app?

With more of us using smartphones, the popularity of mobile applications has exploded. In the digital era, the number of people looking for products and services online is growing rapidly. Smartphone owners look for mobile applications that give them quick access to companies’ products and services. As a result, mobile apps provide customers with a lot of benefits in just one device.

Likewise, companies use mobile apps to increase customer loyalty and improve their services. Mobile Developers are in high demand as companies use apps not only to create brand awareness but also to gather information. For that reason, mobile apps are used as tools to collect valuable data from customers to help companies improve their offer.

There are many types of mobile applications, each with its own advantages. For example, native apps perform better, while web apps don’t need to be customized for the platform or operating system (OS). Likewise, hybrid apps provide users with comfortable user experience. However, you may be wondering how long it takes to develop an app.

To give you an idea of how long the app development process takes, here’s a short guide.

App Idea & Research

app-idea-research

_Average time spent: two to five weeks _

This is the initial stage and a crucial step in setting the project in the right direction. In this stage, you brainstorm ideas and select the best one. Apart from that, you’ll need to do some research to see if your idea is viable. Remember that coming up with an idea is easy; the hard part is to make it a reality.

All your ideas may seem viable, but you still have to run some tests to keep it as real as possible. For that reason, when Web Developers are building a web app, they analyze the available ideas to see which one is the best match for the targeted audience.

Targeting the right audience is crucial when you are developing an app. It saves time when shaping the app in the right direction as you have a clear set of objectives. Likewise, analyzing how the app affects the market is essential. During the research process, App Developers must gather information about potential competitors and threats. This helps the app owners develop strategies to tackle difficulties that come up after the launch.

The research process can take several weeks, but it determines how successful your app can be. For that reason, you must take your time to know all the weaknesses and strengths of the competitors, possible app strategies, and targeted audience.

The outcomes of this stage are app prototypes and the minimum feasible product.

#android app #frontend #ios app #minimum viable product (mvp) #mobile app development #web development #android app development #app development #app development for ios and android #app development process #ios and android app development #ios app development #stages in app development

Mitchel  Carter

Mitchel Carter

1602979200

Developer Career Path: To Become a Team Lead or Stay a Developer?

For a developer, becoming a team leader can be a trap or open up opportunities for creating software. Two years ago, when I was a developer, I was thinking, “I want to be a team leader. It’s so cool, he’s in charge of everything and gets more money. It’s the next step after a senior.” Back then, no one could tell me how wrong I was. I had to find it out myself.

I Got to Be a Team Leader — Twice

I’m naturally very organized. Whatever I do, I try to put things in order, create systems and processes. So I’ve always been inclined to take on more responsibilities than just coding. My first startup job, let’s call it T, was complete chaos in terms of development processes.

Now I probably wouldn’t work in a place like that, but at the time, I enjoyed the vibe. Just imagine it — numerous clients and a team leader who set tasks to the developers in person (and often privately). We would often miss deadlines and had to work late. Once, my boss called and asked me to come back to work at 8 p.m. to finish one feature — all because the deadline was “the next morning.” But at T, we were a family.

We also did everything ourselves — or at least tried to. I’ll never forget how I had to install Ubuntu on a rack server that we got from one of our investors. When I would turn it on, it sounded like a helicopter taking off!

At T, I became a CTO and managed a team of 10 people. So it was my first experience as a team leader.

Then I came to work at D — as a developer. And it was so different in every way when it came to processes.

They employed classic Scrum with sprints, burndown charts, demos, story points, planning, and backlog grooming. I was amazed by the quality of processes, but at first, I was just coding and minding my own business. Then I became friends with the Scrum master. I would ask him lots of questions, and he would willingly answer them and recommend good books.

My favorite was Scrum and XP from the Trenches by Henrik Kniberg. The process at D was based on its methods. As a result, both managers and sellers knew when to expect the result.

Then I joined Skyeng, also as a developer. Unlike my other jobs, it excels at continuous integration with features shipped every day. Within my team, we used a Kanban-like method.

We were also lucky to have our team leader, Petya. At our F2F meetings, we could discuss anything, from missing deadlines to setting up a task tracker. Sometimes I would just give feedback or he would give me advice.

That’s how Petya got to know I’d had some management experience at T and learned Scrum at D.

So one day, he offered me to host a stand-up.

#software-development #developer #dev-team-leadership #agile-software-development #web-development #mobile-app-development #ios-development #android-development

Joseph  Murray

Joseph Murray

1621492530

7 Test Frameworks To Follow in 2021 for Java/Fullstack Developers

It is time to learn new test frameworks in 2021 to improve your code quality and decrease the time of your testing phase. Let’s explore 6 options for devs.

It is time to learn new test frameworks to improve your code quality and decrease the time of your testing phase. I have selected six testing frameworks that sound promising. Some have existed for quite a long time but I have not heard about them before.

At the end of the article, please tell me what you think about them and what your favorite ones are.

Robot Framework

Robot Framework is a generic open-source automation framework. It can be used for test automation and robotic process automation (RPA).

Robot Framework is open and extensible and can be integrated with virtually any other tool to create powerful and flexible automation solutions. Being open-source also means that Robot Framework is free to use without licensing costs.

The RoboFramework is a framework** to write test cases and automation processes.** It means that it may replace** your classic combo Selenium + Cucumber + Gherkins**. To be more precise, the Cucumber Gherkins custom implementation you wrote will be handled by RoboFramework and Selenium invoked below.

For the Java developers, this framework can be executed with Maven or Gradle (but less mature for the latter solution).

#java #testing #test #java framework #java frameworks #testing and developing #java testing #robot framework #test framework #2021

Noah  Rowe

Noah Rowe

1597861200

7 Approaches to Testing - DZone Performance

This article will be interesting for IT directors, product managers, project managers, and anyone who wants to understand the processes of project quality assurance better.

At Qualitica, we test large web and mobile projects, both commercial and national ones. Before a separate testing agency has been established, I spent 10 years as a specialist and head of several digital studios. Usually, in any IT project (websites, applications, games, corporate software), you start by treating testing as a formal procedure. But normally the testing also evolves with the project: the more people are involved, the more complex is the process.

There are 7 testing evolution stages that may differ in different companies:

  1. There are no testers. Their functions are performed by developers or managers.
  2. Testers appear, but test projects only at the completion stage.
  3. Testers check all developer tasks to see if the result matches the original task statement.
  4. Testers are engaged in test design.
  5. A test management tool is being implemented.
  6. Testing automation appears.
  7. The complexity of the hierarchy, the creation of new roles in the test team.

Let’s learn about each stage in more detail.

Stage 1 — Testing Is Performed by the Developer and/or Manager

It’s the simplest, “instinctive” approach to testing. It is common in small companies. When it is impossible or presumably unwanted to hire a professional tester, this part of work is performed in house, but this is an inappropriate and problematic approach for the following reasons:

  • A developer only tests his own scenarios with the data he used in the development process. In this testing, alternative scenarios are omitted. As a result, something is out of control, and end-users usually get errors.
  • A manager takes testing as a side job, having little expertise, time, and desire to do it. This way, you can detect gross errors, but many nuances are overlooked.
  • The subjective approach and the desire to complete the project quickly result in the wish to ignore “minor” problems.

An extreme case is when no testing is done in the company and the error report goes from … the client. Then more and more errors/bugs appear. Thus, clients become testers at their expense.

#testing #testing and qa #testing automation #testing and developing #test