MUGOYA DIHFAHSIH

  Continuous integration (CI) is a practice where a team of developers integrate their code early and often to the main branch or code repository. The goal is to reduce the risk of seeing “integration hell” by waiting for the end of a project or a sprint to merge the work of all developers. One of the primary benefits of adopting CI is that it will save you time during your development cycle by identifying and addressing conflicts early. It’s also a great way to reduce the amount of time spent on fixing bugs and regression by putting more emphasis on having a good test suite. Finally, it helps share a better understanding of the codebase and the features that you’re developing for your customers. The first step on your journey to continuous integration: setting up automated testing. Getting started with automated testing Understanding the different types of tests To get the full benefits of CI, you will need to automate your tests to be able to run them for every change that is made to

UNIT TESTING   is a level of software testing where individual units/ components of a software are tested. The purpose is to validate that each unit of the software performs as designed. A unit is the smallest testable part of any software. It usually has one or a few inputs and usually a single output. In procedural programming, a unit may be an individual program, function, procedure, etc. In object-oriented programming, the smallest unit is a method, which may belong to a base/ super class, abstract class or derived/ child class. (Some treat a module of an application as a unit. This is to be discouraged as there will probably be many individual units within that module.) Unit testing frameworks, drivers, stubs, and mock/ fake objects are used to assist in unit testing. Definition by ISTQB unit testing:  See  component testing. component testing:  The testing of individual software components. Unit Testing Method It is performed by using the  White Box Testing  meth

Here I am sharing 40 best motivational and inspirational quotes from the web that has motivated me to become a developer. These quotes are very inspiring and I felt these will motivate other programmers too and help to avoid common pitfalls in development and hence I thought sharing these quotes with everybody.None of these quotes are mine and please forgive if I have missed to mention the right source. 1.  Dont't worry if it doesn't work right.If everything did, you'd be out of a job.  2.  Don't comment bad code - rewrite it. -  Brian Kernighan 3.  A programming language is for thinking about programs, not for expressing programs you've already thought of. It should be a pencil, not a pen. -  Paul Graham 4.  Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code. - Dan Salomon 5.  It´s better to wait for a productive programmer to become available than it is to wait for the first available prog

Technical documentation in software engineering is the umbrella term that encompasses all written documents and materials dealing with software product development. All software development products, whether created by a small team or a large corporation, require some related documentation. And different types of documents are created through the whole  software development lifecycle  (SDLC). Documentation exists to explain product functionality, unify project-related information, and allow for discussing all significant questions arising between stakeholders and developers. Project documentation by stages and purpose On top of that, documentation errors can set gaps between the visions of stakeholders and engineers and, as a result, a proposed solution won’t meet stakeholders expectations. Consequently, managers should pay a lot of attention to documentation quality. Agile and waterfall approaches The documentation types that the team produces and its scope depending on the s