I work as a lead SDET in a stealth startup and am very active in the testing community. I am focused on testing products and solutions in an efficient and effective fashion covering all phases of the life cycle from requirements through software quality and testing. My hands-on experience, spanning a decade, in designing solutions, and managing software testing projects, enables me to provide valuable insights on processes aimed at improving software quality via the management of technical debt, integrated tests, and continuous, automated test techniques. Connect with me here: https://www.linkedin.com/in/anuraman
My Mentoring Topics
- Software Testing - Concepts, processes, procedures, best practices
- Test Automation using python, java
- py test, rest assured, TestNG framework tips and tricks
- Robot Framework
- API testing
- Postman
- UX testing and principles
- Security testing
- OWASP cheatsheet
r.
15.April 2022It was a very helpful session, i got all of my questions answered.
A.
14.April 2022It was great talking to you. I was really interested in hearing your thoughts on expanding the test automation career and I just wanted to thank you for your time, Anuradha😀 Will follow the path you have shown and connect whenever I have something to discuss 😀
A.
8.April 2022Yes, extremely helpful! I am delighted by the in-depth knowledge she had given me on the very first day. It was a fun, yet pragmatic session on the topic. She gave me day-to-day life examples about how can I optimize UX and observe the users' pain points. Also, she gave me a brief introduction to what it's like to be a UX designer.
r.
11.January 2022Everything went well, I got all my doubts clarified & thanks for the valuable session.
S.
6.January 2022Yes, it was very helpful session. Not at the moment.
Lessons Learned in Software Testing - A Context-Driven Approach
Cem Kaner, James Bach, Bret Pettichord
Key Facts and Insights from "Lessons Learned in Software Testing" Context-driven approach: The book emphasizes the importance of a context-driven approach in software testing, which means that the testing approach should be shaped by the unique circumstances and specific needs of each project. Testing is a skilled activity: The authors assert that testing is a complex, skilled activity that requires creativity, critical thinking, and knowledge in various fields. Tools are just tools: Tools do not perform testing, people do. While tools can be helpful, they should not replace a tester's judgment and analytical skills. Importance of exploratory testing: The book highlights the value of exploratory testing, a technique where testers dynamically design and execute tests while learning from the results. Questioning is a key skill: Testers should continuously question the product and the testing process itself to discover potential problems and improve effectiveness. Testing is not quality assurance: Testing can reveal information about the product's quality, but it can't assure quality. Quality assurance is a broader concept that involves the entire software development process. Testing serves management: The primary purpose of testing is to supply accurate information about the product's quality to help management make informed decisions. Metrics should serve a clear purpose: Any metrics used in testing should be meaningful, relevant, and serve a clear purpose. Effective communication is crucial: Testers need to communicate their findings effectively to be useful, which requires both good writing and interpersonal skills. Continual learning and improvement: Testers should continually strive to improve their skills and knowledge and learn from their experiences. Detailed Analysis and Summary of the Book The book "Lessons Learned in Software Testing" by Cem Kaner, James Bach, and Bret Pettichord is a compendium of experiences and wisdom gleaned from the authors' extensive careers in software testing. It presents a different perspective on software testing, breaking away from the traditional rule-based, process-centric approach to a more flexible, context-driven methodology. The authors argue that software testing is a skilled activity that requires not just technical knowledge but also creativity, critical thinking, and good judgment. This counters the common misconception that testing is a simple, mechanical task that can be fully automated or outsourced to less skilled workers. The context-driven approach is a recurring theme throughout the book. The authors stress that there are no best practices in testing that work for all situations. Instead, testing strategies and techniques should be tailored to the specific context of each project, considering factors such as the product's purpose, the users, the development methodology, and the business environment. The importance of exploratory testing is another significant insight from the book. Unlike scripted testing, exploratory testing allows testers to learn about the product and adapt their testing strategies dynamically, making the process more effective and efficient. However, the book also cautions that tools are just tools. While automated tools can assist in certain aspects of testing, they should not replace human judgment and analytical skills. Tools can't understand context, make decisions, or think creatively, which are crucial for effective testing. A key skill for testers, as the book emphasizes, is questioning. Testers should continuously question the product, the testing process, and even their own assumptions to uncover potential issues and improve the quality of their work. The authors also clarify the often misunderstood relationship between testing and quality assurance. They argue that testing is not quality assurance. Testing can reveal problems and provide information about the product's quality, but it can't guarantee or improve quality. Quality assurance involves a broader range of activities that encompass the entire software development process. An interesting perspective from the book is that testing serves management. The primary purpose of testing is not to find and fix bugs, but to provide useful information to management. This information helps management understand the product's quality, make informed decisions, and allocate resources more effectively. The book also discusses the use of metrics in testing. The authors warn against the misuse of metrics and argue that metrics should serve a clear purpose. They should be meaningful, relevant, and used to improve the testing process, not just for the sake of collecting data. Effective communication is another critical aspect emphasized in the book. Testers need to communicate their findings effectively to be useful. This requires not only good writing skills to write clear and concise bug reports but also interpersonal skills to collaborate with others and advocate for quality. Finally, the authors stress the importance of continual learning and improvement in testing. Testers should strive to learn from their experiences, improve their skills, and stay updated with the latest trends and techniques in the field. In conclusion, "Lessons Learned in Software Testing" offers a fresh and insightful perspective on software testing. It champions a context-driven approach, emphasizes the importance of skilled testing, and provides practical advice on various aspects of testing. It is not just a book for testers, but also for managers, developers, and anyone involved in software development.
ViewAgile Testing - A Practical Guide for Testers and Agile Teams
Lisa Crispin, Janet Gregory
Key Facts Agile Testing is a comprehensive guide that aims to help testers and Agile teams to understand how testing practices can adapt in Agile environments. The authors, Lisa Crispin and Janet Gregory, are recognized experts in Agile testing methodologies. They bring their experience and insights into a resourceful guide. The book emphasizes the importance of collaboration between testers, developers, business people, and customers in Agile environments. Agile Testing frames testing as an integral part of the development process rather than a separate phase. It introduces the Agile Testing Quadrant, a tool that helps teams understand what types of testing are needed and when to employ them. The book outlines the skills and qualities needed for an effective Agile tester, including technical skills, communication skills, and an understanding of the business domain. It provides real-world examples and case studies to illustrate the application of Agile testing principles. Crispin and Gregory advocate for the whole-team approach to quality and testing. The book provides practical strategies to overcome common challenges in Agile testing. Agile Testing promotes the idea that everyone on the team is responsible for quality. The book is a valuable resource for anyone looking to implement or improve Agile testing practices in their teams. Detailed Analysis "Agile Testing: A Practical Guide for Testers and Agile Teams" by Lisa Crispin and Janet Gregory is a comprehensive guide on Agile testing methodologies. As the title suggests, the book is practical and focuses on real-world applications of Agile testing principles. One of the key takeaways from the book is the importance of collaboration. Agile teams are cross-functional, with testers, developers, business people, and customers all working closely together. This collaboration fosters a shared understanding of the project, which in turn helps in delivering a high-quality product. The authors emphasize that everyone on the team is responsible for quality, marking a shift away from traditional testing practices where the responsibility for testing and quality assurance lies primarily with testers. The book introduces the Agile Testing Quadrant, a tool that helps teams decide what types of testing are necessary and when to apply them. The quadrant is divided into four categories: technology-facing tests that guide development, business-facing tests that guide development, technology-facing tests that critique the product, and business-facing tests that critique the product. This tool serves as a guide to ensure that all aspects of testing are covered. In Agile Testing, Crispin and Gregory list the qualities and skills that an effective Agile tester should possess. These include technical skills, communication skills, and an understanding of the business domain. This is consistent with the Agile principle of building projects around motivated individuals, who should be given the environment and support they need and trusted to get the job done. The authors provide numerous real-world examples and case studies that illustrate the application of Agile testing principles. These case studies not only help readers understand the concepts better but also provide them with practical strategies to overcome common challenges in Agile testing. The whole-team approach to quality and testing is another important theme in the book. The authors argue that quality is not solely the responsibility of testers or a separate quality assurance team. Instead, everyone on the team, including developers and business people, should be involved in testing and quality assurance activities. In conclusion, "Agile Testing: A Practical Guide for Testers and Agile Teams" provides a comprehensive and practical guide to Agile testing. It not only introduces the concepts and principles of Agile testing but also provides practical strategies to apply these principles. Whether you're a tester, a developer, or a member of an Agile team, this book is a valuable resource to understand and improve Agile testing practices in your team.
View
M.
28.June 2022Great.