What are the differences between Scrum and Kanban?

-




Comments

Post a Comment

Popular posts from this blog

How to push changes to Git Hub using the command line?

-
Image
Go to the web page for your GitHub repository, and note the URL.  Open  Bash  on Windows. (If you're using Linux or Mac, open  Terminal .)  Use the  cd  command to switch to the directory you want to use to work on your project locally. Enter  git clone [URL of your repository]  to copy your repository to your local machine. Use the  cd  command to go into your repository directory. You'll know you're in the right place if your new command line ends with the name of the main branch of your repository. For example, the name of my main branch is "main," so  (main)  appears at the end of my command line. Once you've added your files to your directory and are ready to push to GitHub, in your  Bash  window, enter  git add .  to select all the files in your repository.  Enter  git commit -m "[commit message]"  to save the changes to your local repository. You can enter anything for the commit m...
Read more

Difference between regression, sanity and smoke tests?

-
Smoke Testing Sanity Testing Regression Testing Performed on initial builds Performed on stable builds Performed on stable builds Tests the stability of a new build Tests the stability of a new functionality or code changes in the existing build Tests the functionality of all affected areas after new functionality /code changes in the existing build Covers end-to-end basic functionalities Covers certain modules, in which code changes have been made Covers detailed testing targeting all the affected areas after new functionalities are added Executed by testers & sometimes also by developers Executed by testers Executed by testers, mostly via automation A part of basic testing A part of regression testing Regression Testing is a super...
Read more

Why is it important to have a detailed bug description with evidence?

-
Having a detailed bug description with evidence is crucial for several reasons: 1. Clear Understanding: Communication: Detailed descriptions help developers and testers understand the issue comprehensively, reducing misinterpretation or ambiguity. Context: It provides the necessary context for the bug, aiding in its reproduction and resolution. 2. Reproducibility: Steps to Reproduce: Clear, step-by-step instructions enable developers to replicate the bug consistently, making it easier to identify its root cause. Evidence: Screenshots, videos, or logs serve as evidence, validating the existence of the issue and assisting in its replication. 3. Efficient Resolution: Faster Resolution: Precise information and evidence expedite the debugging process, allowing developers to pinpoint and fix the issue more swiftly. Reduced Back-and-Forth: Minimizes the need for additional clarification or communication rounds between testers and developers. 4. Quality Improvement: Better Testing: Deta...
Read more