Design a site like this with WordPress.com
Get started

Strategies to writing re-usable test cases

There are two strategies when it comes down to writing reusable test cases: Modularization Modularization is a function-based method of test design where testers categorize functionality to be tested into reusable modules. Testers break down test caes into logical, manageable functions, or modules. These modules are isolated to create independent tests that can then beContinue reading “Strategies to writing re-usable test cases”

When do you write and run automated test scripts?

Many things could go wrong when a new feature or functionality is being developed. It may turn out that the business may change their mind and this feature will be no longer needed. If tests are being automated while the feature is also being developed then the tests may need to be updated many times.Continue reading “When do you write and run automated test scripts?”

Selecting test cases to be automated

When As per the Test Process (STLC), test cases are developed during the Test Design activity. Once all the requirements have been gathered, analysed and the test cases have been developed. This is exactly the time to decide on which test cases to be automated. How Not all test cases will be automated. The followingContinue reading “Selecting test cases to be automated”

Continuous Integration, Continuous Delivery, Continuous Deployment and Continuous Testing

Continuous integration is a software development practice where developers regularly merge their code changes into the central repository (VCS). This activity triggers automated builds and tests to be run. The goal is to find bugs earlier, improve software quality and reduce time to validate and release new software updates. Continuous delivery automates the entire softwareContinue reading “Continuous Integration, Continuous Delivery, Continuous Deployment and Continuous Testing”

How agile scrum overcomes the drawbacks of waterfall?

Agile scrum is an iterative and incremental software development model. This means that they are building smaller blocks of software and involve stakeholders for earlier feedbacks/reviews. This means that they can reduce the delivery time as well as ensure a high customer satisfaction due to higher software quality. There is no lengthy documentation process whichContinue reading “How agile scrum overcomes the drawbacks of waterfall?”

Difference between agile scrum and kanban?

For scrum, there is a fixed sprint length of 1 – 4 weeks but on the other hand, kanban aims to achieve continuous flow i.e. there is no set time. This also means that at the end of the sprint, a scrum team would have developed a working software that could be shipped. For kanban,Continue reading “Difference between agile scrum and kanban?”

What are the roles in agile scrum?

Scrum master – Most similar to a project manager in other software development model, scrum master is responsible for supporting the development team, clearing organizational roadblocks, facilitate scrum team meetings and check in with the team and ensuring that the tasks are completed on time.Product owner – Product owner represents the stakeholders of the project.Continue reading “What are the roles in agile scrum?”