Sick of seeing bugs in your SDLC? Host a scrum meeting, advises Shiva Kumar, Scrum Master and Mobile Application Tester at IDrive Software India Pvt Ltd
Kumar has been working as a Software Tester for the last 8 years on both web and native mobile apps; prioritising bug reporting through scum meetings while taking part in requirement discussions and tasks for writing and executing test cases.
“Scrum meetings are particularly useful for ensuring bugs are found before the end of a SDLC. We at IDrive use the meeting room and timings to pass updates securely and to cross-check all acceptance criteria; ensuring test cases and scenarios are mapped before the end of a sprint on a daily basis,” reveals Kumar.
Scenario bugs & requirements
“By implementing scrum, business scenario bugs and requirements should work how they’re supposed to. Nevertheless, a few bugs are likely to escape environmental, data related issues.”
To safeguard security measures, Kumar uses Captcha to help avoid a DDoS attack. According to him, it’s also important to email notifications if a server goes down.
“A health check on memory leakage and server related concerns is a part of our smoke tests. This can take up to one hour and ensures all basics are working how they should be,” he adds.
Automation vs. manual testing
When analysing the metrics and context of a project, Kumar believes there are only a few metrics the company doesn’t follow which includes standard or mandatory metrics. Instead, it’s all about automation.
“Automation scripts can be extremely useful for finding broken features in continuous integration. When writing automated tests fewer issues are typically found. Despite this, we at IDrive still excel in manual testing concepts,” continues Kumar.
He also notes that manual testing will remain the same, but its approaches and methodologies are likely to change.
Written by Leah Alger
