Sreenivas Mothukuru

Article written by   Sreenivas Mothukuru Anybody can develop software applications but only QA can better test and certify applications. During QA validation test engineers perform various types of tests to ensure developed application is as per the requirements/specifications. The tests include manual checks to some extent and automation then onwards. Now days the term "automation" has gained lot of significant in Software Industry. Most of the Software professional’s know automaton as some kind of testing done at browser level. At Browser level automation QA engineers automate repetitive tasks and test operations performed on the web browser. Test Engineers have to constantly adapt and modify the script if the web page layout changes. Good number of tools such as QTP, Silk Test, Selenium, etc. support automation. But, are we doing good job testing web applications only at browser level? The answer is   NO . This approach is like taking same pill for any illness! Cho...

Article written by  Sreenivas Mothukuru 1)       Ignore tools and look for reasons: Instead of using / appreciating the features which specialized tools provide teams start overlooking the tools and complain about the features. 2)       Result in “over commitment” or “under commitment” or “as per the commitment”: Due to point 1, team members pull user stories based on their gut feeling. This might result in a) over commitment b) under commitment c) as per the commitment at the end of the sprint. 3)       User stories will be de-scoped from the Sprint: Due to point 1 & 2, teams commit for 'N' user stories and complete N - n (n = 0 to N). In every sprint pulling user stories out will gradually impact the confidence level of scrum teams and decrease team's velocity. 4)       Lose focus on Quality: Sometimes team run after doing more ... more ... more and finally los...

What is Agile? Agile methodologies generally promote a project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages team work, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. In brief, agile encourages ·          Individuals and interactions over processes and tools. ·          Working software over comprehensive documentation. ·          Customer collaboration over contract negotiation. ·          Responding to change over following a plan. There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cy...