Author Archives: cryong

Impact analysis evaluates the changes that were made to a system/application to identify the intended consequences as well as possible side effects of a change and to identify the areas in the system that will be affected by the change.This means that impact analysis should be done before a change is made to help decideContinue reading “Impact analysis – when and how does it improve quality”

Release notes is a document that is released as part of the final build that contains new enhancements/changes and the defect fixes as part of that build.

Typical tasks that tester performs may include: Reviewing test plans Analysing, reviewing and assessing requirements, specifications and other test artifacts Design and execute test cases Prepare test data Evaluate results from test case executions

Organisations may need their own separate testing teams. Here are couple of possible reasons as to why this is so: They are more likely to recognize different kinds of failures because of their perspectives and biases. They are able to verify, challenge or disprove assumptions made by stakeholders during specification and implementation of the system.

There are many benefits that comes with adopting Agile methodology. These include but not limited to: Higher product quality – In Agile development, testing is integrated during the cycle, which means that there are regular checkups to see that the product is working during the development. This enables the product owner to make changes ifContinue reading “Benefits of adopting Agile methodology”

Testing occurs from the get-go i.e. unlike waterfall where we test after the development, it occurs side-by-side with development. Also note that the responsibility is shared between all the members of the scrum team, this means that the developers in the team may also carry out testing.

A change request is a proposal to a modification to a product or system.Below are the process for handling a change request once it has been documented and received: Information gathering step where more change request details are requested if they are lacking and any ambiguities and mistakes are clarified and fixed. Once enough informationContinue reading “Process for handling change request”

Root cause analysis is a systematic process for finding and identifying the root cause of a problem or event. The 5-whys method/technique involves one asking “why?” five times in a row to identify the root cause of the problem.

Regression is a type of testing that gets performed to ensure that a change made to the system has not broken the existing functionality of the system. It is done after an enhancement or defect fixes are made to the system. Impact analysis is required to identify possible impacted areas due to those changes.Selecting testContinue reading “Regression test cases identification”

Defects do reoccur if the symptoms are treated instead of the underlying causes. The root cause is often a failed control, process, or a gap in staff skill sets that caused an earlier condition or event. Root Cause Analysis is carried out in order to tackle this problem.There are two approaches/methods to RCA: Fishbone diagramContinue reading “Preventing recurring defects”