Skip to content

Basic PHP, Symfony interview test for candidates as a backend developer.

Notifications You must be signed in to change notification settings

mubasharkk/basic-symfony28-interview-test

Repository files navigation

Basic PHP and Symfony 2.8 interview

Dear candidate, please follow this readme and solve all questions.

Before you can start, you should prepare your development environment.

Using Symfony with Homestead/Vagrant

In order to develop a Symfony application, you might want to use a virtual development environment instead of the built-in server or WAMP/LAMP. Homestead is an easy-to-use Vagrant box to get a virtual environment up and running quickly.

Before you can use Homestead, you need to install and configure Vagrant and Homestead as explained in the Homestead documentation.

Resources:

This test requires:

Tip: Install Robomongo on your OS

Tip: Clone the test repository and make sure its working. Access the project with your favourite browser. You should see similar welcome screen. Dont forget to run composer install. Symfony welcome screen

Help: PHP 5.6+ (debian/ubuntu)

sudo apt-get install -qq php5-cli php5-fpm php5-mysqlnd php5-curl php5-gd php5-json php5-redis php5-imap php5-intl php5-imagick php5-mcrypt php5-xdebug php5-xmlrpc php5-xsl php5-twig php5-mongo php5-dev

Help: (optional) PECL MongoDB library (debian/ubuntu)

sudo apt-get install pkg-config libssl-dev && sudo pecl update-channels && sudo pecl install mongodb

Good luck!


Test tasks:

  1. Change the text on symfony homepage from "Welcome to Symfony 2.8.8" to "This is a test"

  2. Run the PhpUnit test. Check if there are any errors, if so fix them.

  3. Create a new Bundle "InterviewBundle" within the namespace "Test"

  4. Create a method helloAction under AppBundle\Controller\DefaultController

  • for route /hello
  • with a proper json return {"hello":"world!"}
  1. Create a "Bios" collection and load the example data into your MongoDB server
  • copy the json string from mongodb website (link)
  • or download and load the archive dump (link)
  1. Define ODM "Bios" document under namespace Test/InterviewBundle/Documents

  2. Define ODM "Bios" repository under namespace Test/InterviewBundle/Repositories

  3. Implement following repository methods

  • findByFirstName($firstName)
  • findByContribution($contributionName)
  • findByDeadBefore($year)
  1. Define and create a service "BiosService" under namespace Test/InterviewBundle/Services and implement following methods
  • getAllAwards()
  • Use the logger to log operations (error, warning, debug)
  1. Create ContributionsController under namespace Test/InterviewBundle/Controller

  2. Add a contributionsAction method to your ContributionsController

  • for route /contributions
  • make a use of your BiosService
  • avoid logic under controller
  • method should list all contributions
  • with a proper json return ["contrib", ...]
  1. Add a biosByContributionAction method to your ContributionsController
  • for route /contributions/{contributionName}
  • make a use of your BiosService
  • avoid logic under controller
  • method should list all bios documents with provided contribution
  • with a proper json return [{...}]
  1. make a unit test for the controller
  • check if route /hello has response code 200
  • check if route /hello response is a json
  • check if route /contributions has response code 200
  • check if route /contributions/fake has response code 404
  • check if route /contributions/OOP has response code 200
  1. make a unit test for the BiosService
  • at least 1 method of your choice
  1. write a command called test:command that should accept 1 argument called id under namespace Test/InterviewBundle/Command
  • The command should check if a Bios document with an id of the argument exists
  • if document exists, return info "document exists"
  • if document doesnt exist, return error "document doesnt exist"

Bonus tasks

  1. Go to app/config/config.yml and add the following yaml structure. (NOTICE: ping is as child-key of test)
test:
  ping: pong
  1. Check the symfony application for errors and fix them if any.

  2. write a prompt for the command test:command

  • Prompt text is "This is a test. Do you want to continue (y/N) ?"
  • If you decline, return error "Nothing done. Exiting..."
  • If you accept, run the command

That's it!

Thank you for your participation! Good luck submitting your results!

About

Basic PHP, Symfony interview test for candidates as a backend developer.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published