The first contact with a third-party project takes place according to our corporate approach
3. Creating a copy of the project on a separate server. This is done in order to eliminate the risk of breaking the main project due to the applied changes in the code. Sometimes applied changes can cause conflicts in the code and this will lead to a partial breakdown of the project's functionality. For example, a developer made changes to the code for the “select quantity of goods” functionality and this change negatively affected the functionality of the shopping cart.
! We will look at the methods of testing code at the Back End and Front End using Jasmine software in the next article.
Sending a query to MySQL from the Front End part to check the health of the database (DB)
Researching the project code.
As a rule, from the moment the first task is set and until the moment when you are ready to start working with the code, it takes 16-20 hours to study the code. This time includes:
- search for the code of that part of the project on the Front End side, with which you need to work at the moment. The developer reviews the html / css code and gains the necessary understanding of the organization of the code at this point. It will take 4-8 hours to study.
- search for the code on the Back End side, with which the Front End is connected according to the task facing the developer.
It will take 8-20 hours to study.
Implementation of the first task.
After studying the project code, the developer makes an estimate of the time spent on the first task and submits it to the project manager.
! We wrote an article about project management earlier.
The project manager adds a rating to the Trello or Jira board and notifies the customer about it.
After agreeing on the assessment with the customer, the project manager transfers the task to the "In Progress" section and the developer receives a notification about the need to start this task.
After completing the work, the developer marks the status “Finish” on the board and the project manager transfers the task to the status “Testing”.
After this step, the developer runs the Git tests and gets the result. Read more about Git in the previous article.
If the test was successful and no errors were found in the code, then the task is transferred to the “Finished” status and the code can be applied on the main project without the risk of breaking the project.
If the test results show errors, then the task is moved to the "In progress" status and the developer starts it again. In Airkod's practice, the code passes tests the first time.
TECHNOLOGIES WE USE FOR DEVELOPMENT PROCESS
PHP is a popular general-purpose scripting language that is especially suited to web development. Fa
Laravel is a web application framework with expressive, elegant syntax.
Node.js is a platform for building fast and scalable network applications. Node.js uses an event-dri
Angular is a platform for building mobile and desktop web applications
Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displa
React is a library for building composable user interfaces, it supports and encourages the creation
MySQL is an Oracle-backed open source relational database management system (RDBMS) based on Structu
MongoDB is a cross-platform document-oriented database program. Classified as a NoSQL database progr
Redis (Remote Dictionary Server) is an in-memory data structure project implementing a distributed,