Skip to main content

Posts

Showing posts from January, 2018

How I cleared ISTQB Agile Extension Certification?

In this post I am going to share my experience and preparation for ISTQB Agile Foundation Level exam. The pre-requisite for this exam is ISTQB Foundation Level Certificate. This is an extension exam since it deals with only Agile development. Who is eligible for this exam? Every Tester who has ISTQB foundation level certificate is eligible. If you are planning to work in an agile environment or your current job demands so then you must go for this certificate since it will give you a basic idea of how Agile development works. What you will learn from the certification? After completing the certification, you will be able to understand how testing is a crucial part in agile. Role of a tester, how as a tester you can make a difference. Difference between Agile and Traditional methods. You will also learn about agile values and principles, continuous integration, planning, Kanban, XP and scrum methods. What is the exam structure? Exam consists of total 40 questions with multiple...

All About Continuous Integration in Agile

In my last post,  Benefits of Early and Frequent Feedback in Agile development  I mentioned how Continuous Integration helps in early and frequent feedback. In this post, we are going to go deeper into the concept and see what exactly it does, how it does and its benefits and challenges. Continuous Integration is an automated system which wraps configuration management, software build, deployment and testing into one repeatable process. The best practice is to run the whole set of set into the new build (with all the new code check ins) at least once a day. This gives a feedback on the  build quality. If all the automated tests passed then the build can be used to perform deeper testing. Below are some of the activities carried out by CI: Code analysis Compilation of code and generating an executable file Perform Unit testing Deploying the build onto the testing environment Performing integration testing Generating reports In our project, nightly build and...

Benefits of Early and Frequent Feedback in Agile development

One of the reasons why Agile is preferred over traditional development method is "Early and Frequent Customer Feedback". This is not only helps customer to get what he wants but also helps development team to understand the requirement better. There is no room for misunderstandings and delays. so no BAD CUSTOMER SERVICE! In this post, I am going to discuss about some of the major benefits of early and frequent feedback in Agile. One way to get the early feedback is "CI" or Continuous Integration. There are many tools available in the market like Jenkins which help in running automated tests when a change is introduced in the build and give the feedback on the build performance or quality. Below are some of the advantages of early and frequent feedback: Early and regular feedback helps in clearing out the misunderstanding of the requirements. Unlike in traditional method, fixing the issues or requirements change is a lot less expensive. Customer get to see the...

Exploratory Testing in Agile

Exploratory testing plays an important role in Agile environment due to limited time available and limited details of the user stories. To get the best results out of exploratory testing, it should be combined with other experience based testing techniques. Some of the important features of exploratory testing in agile are: Test design and execution take place at the same time guided by prepared Test Charter The result of most recent tests are used to guide the next tests. As mentioned earlier, it is combined with other experienced based testing in order to get the best results It is a time boxed testing session and test charter provides the test conditions to cover.  Test Charter Test Charter is a statement of test objectives and test ideas (how to test) and mainly used in carrying out the exploratory testing. Below are some of the details included in preparing Test Charter: Actor : the expected user of the system Setup : the test environment set up needed to ca...