Quality Assurance

The following steps in our process ensures that the highest standards are met and that your projects are delivered in time and to the standards you would expect from a company like putITout:

Information flow

It is fundamental to our business to keep you abreast of progress and to maintain constant communication from client to project manager to the developer. We use project management software in order to ensure the whole process is properly monitored and reported. The progress of a project is always easily traceable and key deadlines and milestones are clearly defined in the initial scoping stage.

Beyond the project management software, we make it our practice to have regular update meetings with our clients. We usually like to come to your offices up to twice a week, for an hour or so, to work through the progress of a project, voice any concerns on either side and gather and deliver any information needed from both sides and any changes that the client is looking to implement. This practice is important as it instills confidence in both parties and increases the ease of information flow.

Planning

We insist on a suitable planning stage before any project commences. It is important that a project is as well defined as possible in advance and that there is a project plan that clearly sets out key deliverables and milestones and also highlights the assumptions and risks of the project.

Developing

As soon as we can, once the development has begun, we initiate unit testing on our code. The testing product required for a project depends on the technology used, but this initial stage of testing is vital in order to ensure that the code is of the highest quality right from the beginning.

Internal testing (Quality Assurance)

During the QA phase, our UI (user interface) testing is employed (if necessary). We tend to use Selenium for our UI testing. At this stage, we also commence with our regression testing.

UAT

Once the project has been delivered, there will be a period of UAT (user acceptance testing), where any remaining bugs will be picked up by the client, who must allocate sufficient time to this stage themselves. We structure this phase into a feedback loop. We insist that bugs are identified in bulk, ie the client lists all the bugs they can find, deliver that to us in one go and we work through that list. This proves much more efficient for all parties than reporting bugs on an ‘as found’ basis.