Many kinds of testing exist. Brian Marick came up with the Agile Testing Quadrant as shown below. In this diagram, he categorized tests according to whether they are business facing or technology facing and whether they support the development process or are used to critique the project. Q1-Technology Facing Tests that Support the Development Process […]
Read MoreA software system may be tested at different levels. Typical test levels are, from the base of the pyramid to the top, unit, integration, system, and acceptance. The test pyramid emphasizes having a large number of tests at the lower levels (bottom of the pyramid) and, as development moves to the upper levels, the number […]
Read MoreAgile projects often involve heavy use of automated tools to develop, test, and manage software development. Developers use tools for static analysis, unit testing, and code coverage. Developers continuously check the code and unit tests into a configuration management system, using automated build and test frameworks. These frameworks allow the continuous integration of new software […]
Read MoreBecause requirements in Scrum are only loosely defined, they need to revisited and clearly defined before they come into the Sprint. This is done during the current sprint in a activity called Product Backlog Refinement. Duration of the PB Refinement The guidelines in Scrum is to usually spend 10% of the Development Team effort in […]
Read MoreInfrastructure as code (IaC) is the process of managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. Both physical equipment such as bare-metal servers as well as virtual machines and associated configuration resources are called “infrastructure”, although they have nothing to do with actual infrastructure. The definitions may be in a version control system. It […]
Read MoreJenkins Tool is a software that allows continuous integration. Jenkins tool will be installed on a server where the central build will take place. The following flowchart demonstrates a very simple workflow of how Jenkins works. Along with Jenkins tool, sometimes, one might also see the association of Hudson. Hudson is a very popular open-source Java-based continuous […]
Read MoreOne of the important parts of any DevOps process is the regular release of working software. In Scrum, iterations tend to be only one or two weeks long. When you use Kanban you release whenever a reasonable package is ready – often multiple times a week. When you do that, you will inevitably see that […]
Read MoreIn Continuous integrations, all the developer work is merged to main branch several times a day. This helps in reducing integration problems. In Continuous integration we try to minimize the duration for which a branch remains checked out. A developer code gets early feedback on the new code added to main repository by using Continuous Integration. […]
Read MoreContinuous deployment can be thought of as an extension of continuous integration and Continuous Delivery aiming at minimizing lead time, the time elapsed between development writing one new line of code and this new code being used by live users, in production. To achieve continuous deployment, the team relies on infrastructure that automates and instruments the various steps […]
Read MoreManaging Regression Risk with Evolving Manual and Automated Test Cases In an Agile project, as each iteration completes, the product grows. Therefore, the scope of testing also increases. Along with testing the code changes made in the current iteration, testers also need to verify no regression risk has been introduced on features that were developed […]
Read More