The Agile Manifesto first appeared in 2001. It sought to alter the software creation process. The manifesto has four key aspects, but few people are aware of the 12 Agile Principles. They provide more specific explanations of the process in which agile product development can be carried out. After many years, nearly all companies claim that they provide "agile services", but most only pay lip service to the Agile Manifesto's ideas and concepts. The software development industry has also evolved dramatically. It's worth revisiting the agile standards to check their meanings and whether they're still relevant.Timely and Consistent Delivery of ... Read More

This guide presents the seven fundamental Software Testing Principles that any software tester and quality assurance professional should understand.6 Principles of Software TestingExhaustive testing is not possibleEarly testingDefect clusteringPesticide paradoxTesting is context-dependentAbsence of errors fallacyBackgroundWhen performing software testing, one must achieve optimal test results without straying from the target. But how do we know if we are using the best research strategy? To do so, we must adhere to certain fundamental research standards.Consider the following circumstance: we are transferring a file from Folder A to Folder B. Consider all of the many ways by which we can test this.Aside from ... Read More

There are two types of computing methods namely, soft computing and hard computing. The basic difference between the two is that the hard computing is a conventional computing method which relies on the principles of certainty, accuracy, and inflexibility, on the other hand, the soft computing is a modern methodology that relies on the principles of approximation, flexibility, and uncertainty. In this article, we will discuss the important differences between soft computing and hard computing. But, before going into the differences, let's start with a basic overview. What is Soft Computing? Soft Computing is a modern computing model that ... Read More

Cloning a repository involves downloading a copy of the source code from source control. In other words, cloning is creating a copy of an existing repository. Consider an example where multiple users are working on a project. This feature can be used by the users to create a development copy.If you have a GitHub repository, you need to first invite collaborators into the repository. Each collaborator will then clone the repository into their local machines.Locally they will work with this cloned repository, make local changes and perform commits on it. Once they are ready to share their changes with others ... Read More

Even if you have a public repository in GitHub, not everyone has the permission to push code into your repository. Other users have a read-only access and cannot modify the repository. In order to allow other individuals to make changes to your repository, you need to invite them to collaborate to the project.The following steps should be performed to invite other team members to collaborate with your repository.Step 1 − Click on the Settings tab in the right corner of the GitHub page.Step 2 − Go to Manage Access option under the Settings tab. On the Manage Access page, you ... Read More

A GitHub account is a pre-requisite for creating a GitHub repository. Follow the below steps after registering with GitHub.Step 1 − Login to the GitHub account. Once you login to your account you will see a ‘+’ button on the right. Click on the button and select "New repository" option to create a new repository.Configure the following in the create a new repository page.Repository name: GitHub will validate the repository name that you have entered.Type of the repository: GitHub lets you create the following types of repositories −Private repository − Private Repository is the one that can be accessed only ... Read More

Version control systems are of two types - centralized and distributed. In a centralized system there will be one single repository that is shared by all team members. Problem with this system is that if the central repo goes offline then all people dependent on the central repo will be affected.In git each person has a repository which means they are not dependent on the central server. They can work offline with this model. But how can we collaborate with this model? Synchronizing with each user of the repository would take time but we can have a better workflow which ... Read More

Cherry picking is a way to choose specific commits from one branch and apply them to another branch. This is useful when you want to select specific changes from a pull request.git cherry-pick {commit_hash}The above command will cherry pick the commit associated with the specified commit hash to the current branch.From the above commits shown in the diagram, we need to apply only commit F1 from the feature branch to the master branch.In this case, the master branch after cherry picking will look as below.Example$ dell@DESKTOP-N961NR5 MINGW64 /e/tut_repo $ git init Initialized empty Git repository in E:/tut_repo/.git/ $ dell@DESKTOP-N961NR5 ... Read More

Rebasing alters a sequence of commits. It moves or relocates a sequence of commits from current branch to the target branch. By default, the commits from the current branch that are not already on the other branch are rebased. Rebasing technique allows us to keep a linear history.Let us understand from this from the diagram below.To rebase we need to be in the branch which needs to be rebased into the target. In our scenario, we need to execute the rebase command on the feature branch. After executing the rebase command we will get a linear history.After executing the rebase ... Read More

Imagine if your feature branch has large number of commits- E.g. 100s commits. Rather than merging all commits individually from feature to master, there is an option to add up all commits into a single commit. This is called a squash commit because it "squashes" all the individual commits into one big change. As far as the history of the master branch is concerned, the history of the feature branch would be lost.We can use the following command to squash-merge the commits of a branch to the master branch.$ git merge --squash feature_branchThe diagram shows that we have 3 commits ... Read More