The document provides a professional synopsis and experience summary for K S Mary Deepthy. It details her 10 years of experience in testing, test planning, and managing testing teams. She currently works as a Senior Technical Lead at UST Global, where she leads teams of up to 36 people in testing projects for clients like Google and Intel. Her experience includes test automation, test case development, defect analysis, and ensuring high quality product releases through rigorous testing.
DURGASOFT is INDIA's No.1 Software Training Center offers online training on various technologies like JAVA, .NET, ANDROID,HADOOP,TESTING TOOLS , ADF, INFORMATICA,TALLEAU,IOS,OBIEE,ANJULAR JA, SAP...courses from Hyderabad & Bangalore - India with Real Time Experts.
The document outlines the software testing life cycle (STLC) which includes 10 phases: 1) requirement analysis, 2) prepare test plan, 3) test case designing, 4) design review, 5) code review, 6) test case execution, 7) bug reporting and regression testing, 8) inspection and release, 9) client acceptance, and 10) test summary analysis. It then provides details on requirement analysis, preparing the test plan, roles and responsibilities, and guidelines for developing an effective test plan. The test plan is a strategic document that defines the testing objectives, scope, approach, resources, and schedules to ensure software quality.
Software Testing and Quality Assurance Assignment 3Gurpreet singh
Short questions :
Que 1 : Define Software Testing.
Que 2 : What is risk identification ?
Que 3 : What is SCM ?
Que 4 : Define Debugging.
Que 5 : Explain Configuration audit.
Que 6 : Differentiate between white box testing & black box testing.
Que 7 : What do you mean by metrics ?
Que 8 : What do you mean by version control ?
Que 9 : Explain Object Oriented Software Engineering.
Que 10 : What are the advantages and disadvantages of manual testing tools ?
Long Questions:
Que 1 : What do you mean by baselines ? Explain their importance.
Que 2 : What do you mean by change control ? Explain the various steps in detail.
Que 3 : Explain various types of testing in detail.
Que 4 : Differentiate between automated testing and manual testing.
Que 5 : What is web engineering ? Explain in detail its model and features.
The key to successful testing is effective and timely planning. Rick Craig introduces proven test planning methods and techniques, including the Master Test Plan and level-specific test plans for acceptance, system, integration, and unit testing. Rick explains how to customize an IEEE-829-style test plan and test summary report to fit your organization’s needs. Learn how to manage test activities, estimate test efforts, and achieve buy-in. Discover a practical risk analysis technique to prioritize your testing and become more effective with limited resources. Rick offers test measurement and reporting recommendations for monitoring the testing process. Discover new methods and develop renewed energy for taking your organization’s test management to the next level.
This document provides an overview of software testing concepts, including:
- Definitions of software testing and related terms
- The software testing process, including test planning, preparation, execution, reporting, and analysis
- Types of testing such as unit, integration, system, and acceptance testing
- Tester competencies including both soft skills and technical testing skills
- Common testing documents and resources used
Research Activities: past, present, and future.Marco Torchiano
Public seminar for Professor Position at Politecnico di Torino
- past research products
- current research activities
- future outlook
October 19, 2018
The document provides an overview of manual testing and the software development lifecycle. It defines key terms like software testing, verification and validation. It discusses different types of testing like static testing, white-box testing and black-box testing. It also explains software quality concepts like quality assurance and quality control. The document then introduces process standards like ISO and CMMI and maturity models. It describes various software development life cycle models like waterfall, prototyping and incremental development.
Software, Types of Software
Software Project, Application and Product
Software Business Process
SDLC
SDLC Models
Test Levels
Software Environment
Test Types
Test Design Techniques
Testing Process (STLC)
Informal Testing
Quality Standards
Software Business Domains
DURGASOFT is INDIA's No.1 Software Training Center offers online training on various technologies like JAVA, .NET, ANDROID,HADOOP,TESTING TOOLS , ADF, INFORMATICA,TALLEAU,IOS,OBIEE,ANJULAR JA, SAP...courses from Hyderabad & Bangalore - India with Real Time Experts.
The document outlines the software testing life cycle (STLC) which includes 10 phases: 1) requirement analysis, 2) prepare test plan, 3) test case designing, 4) design review, 5) code review, 6) test case execution, 7) bug reporting and regression testing, 8) inspection and release, 9) client acceptance, and 10) test summary analysis. It then provides details on requirement analysis, preparing the test plan, roles and responsibilities, and guidelines for developing an effective test plan. The test plan is a strategic document that defines the testing objectives, scope, approach, resources, and schedules to ensure software quality.
Software Testing and Quality Assurance Assignment 3Gurpreet singh
Short questions :
Que 1 : Define Software Testing.
Que 2 : What is risk identification ?
Que 3 : What is SCM ?
Que 4 : Define Debugging.
Que 5 : Explain Configuration audit.
Que 6 : Differentiate between white box testing & black box testing.
Que 7 : What do you mean by metrics ?
Que 8 : What do you mean by version control ?
Que 9 : Explain Object Oriented Software Engineering.
Que 10 : What are the advantages and disadvantages of manual testing tools ?
Long Questions:
Que 1 : What do you mean by baselines ? Explain their importance.
Que 2 : What do you mean by change control ? Explain the various steps in detail.
Que 3 : Explain various types of testing in detail.
Que 4 : Differentiate between automated testing and manual testing.
Que 5 : What is web engineering ? Explain in detail its model and features.
The key to successful testing is effective and timely planning. Rick Craig introduces proven test planning methods and techniques, including the Master Test Plan and level-specific test plans for acceptance, system, integration, and unit testing. Rick explains how to customize an IEEE-829-style test plan and test summary report to fit your organization’s needs. Learn how to manage test activities, estimate test efforts, and achieve buy-in. Discover a practical risk analysis technique to prioritize your testing and become more effective with limited resources. Rick offers test measurement and reporting recommendations for monitoring the testing process. Discover new methods and develop renewed energy for taking your organization’s test management to the next level.
This document provides an overview of software testing concepts, including:
- Definitions of software testing and related terms
- The software testing process, including test planning, preparation, execution, reporting, and analysis
- Types of testing such as unit, integration, system, and acceptance testing
- Tester competencies including both soft skills and technical testing skills
- Common testing documents and resources used
Research Activities: past, present, and future.Marco Torchiano
Public seminar for Professor Position at Politecnico di Torino
- past research products
- current research activities
- future outlook
October 19, 2018
The document provides an overview of manual testing and the software development lifecycle. It defines key terms like software testing, verification and validation. It discusses different types of testing like static testing, white-box testing and black-box testing. It also explains software quality concepts like quality assurance and quality control. The document then introduces process standards like ISO and CMMI and maturity models. It describes various software development life cycle models like waterfall, prototyping and incremental development.
Software, Types of Software
Software Project, Application and Product
Software Business Process
SDLC
SDLC Models
Test Levels
Software Environment
Test Types
Test Design Techniques
Testing Process (STLC)
Informal Testing
Quality Standards
Software Business Domains
5WCSQ - Quality Improvement by the Real-Time Detection of the ProblemsTakanori Suzuki
1. The document discusses quality improvement in software development projects through real-time detection of problems. It describes current high failure rates in projects and how quantitative management can help.
2. It introduces the "Development ForeCast" approach which uses automated measurements, monitoring, and analysis of source code metrics to detect quality problems in real-time. This allows risks to be identified early.
3. Case studies show how static code analysis tools can evaluate quality at different stages of development, like identifying modules likely to have defects during testing. Real-time monitoring of metrics can improve quality while reducing costs.
The document provides an introduction to software testing fundamentals and artifacts. It discusses test cases, test specifications, test planning, and test execution. Test cases are defined as a set of test inputs, execution conditions, and expected results to test a specific objective. Good test cases should be reasonable, exercise areas of interest, and make failures obvious. The document outlines steps for creating test cases such as breaking the application into testable modules, writing checklists, adding questions, and getting reviews from other testers and developers.
This document provides an overview and introduction to software testing for beginners. It discusses what software testing is, why it's important, and what testers do. Some key points covered include:
- The goal of testing is to find bugs early and ensure quality by designing and executing test cases that cover functionality, security, databases, and user interfaces.
- A good tester has skills like communication, organization, troubleshooting, and being methodical and objective in their work.
- Testing occurs at all stages of the software development life cycle from initial specifications through coding, testing, deployment and maintenance.
This document summarizes Rex Black's book on risk-based testing strategies. It discusses:
- The two main types of risks in testing: product risks related to quality, and project risks related to management and schedules.
- How risk-based testing guides testing activities based on identified risks, prioritizing higher-risk items and allocating more testing effort to them.
- The benefits of risk-based testing over requirements-based testing, like having a more predictable reduction in risk over time and the ability to intelligently reduce testing if needed.
- The history of risk-based testing strategies dating back to the 1980s, and how modern approaches aim to systematically analyze and address risks.
The document discusses software testing concepts and processes. It covers definitions of testing, objectives of testing, types of defects and their costs. It also describes the typical software testing process which includes test planning, preparation, execution, reporting and defect tracking. Additionally, it discusses test strategies such as unit testing, integration testing, system testing and acceptance testing. The overall purpose is to provide an introduction and overview of basic software testing concepts.
Agile/Scrum best Practices to improve quality.If some testing finds some defects, lot of testing would find lot of defects and improve quality. This presentation talks about few testing best practices that an agile team should follow for quality PI.
This document discusses exploratory testing and defines it as "Any testing to the extent that the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests." It describes how all testers do some exploratory testing. Exploratory testers rely on a variety of knowledge, including knowledge of specific domains, risks, and testing techniques. Exploratory testing can differ based on a tester's personality and experiences. Questioning strategies like the Phoenix Checklist can help exploratory testers generate effective questions to test software.
Christian Ramírez presented on software testing considerations for mobile banking applications. Key points included separating test logic from technical drivers, using test automation frameworks, and adopting test design approaches like TDD and BDD. Best practices involved continuous integration, model-based testing, and leveraging tools for code analysis and cross-browser testing. The presentation provided guidance on effective strategies for testing mobile apps across different platforms and environments.
Sharad is a senior software engineer with over 4 years of experience in testing medical devices. He has extensive experience in both automation and manual testing as well as developing automation frameworks using LabVIEW. His resume highlights 3 projects with clients Physio Control and Animas Corporation where he performed roles such as developing automated test equipment, verifying software requirements, and ensuring medical devices received regulatory approval. He is proficient in languages like LabVIEW, operating systems like Windows, and testing skills including requirements analysis and defect tracking tools.
This document discusses innovations and adaptations in agile testing. It covers agile testing roles and practices like testing early and often, automating tests, and continuous integration. It discusses challenges like testing exploratory and non-functional requirements within sprints. One approach presented is to test these in parallel with a sprint lag through dedicated test phases. This reduces risks of critical defects found late impacting releases. The document also discusses adaptations like managing test environments, skills development, and indicators to optimize agile testing.
Objectives:
1. To understand software testing and its importance.
2. To understand the concepts of software quality.
3. To see the different classes/ levels/ types of testing.
4. To see the different test case design techniques.
5. To understand the software processes related to testing in a typical software organisation.
Rick Craig, a consultant with over 30 years of experience in testing and test management, presented a training on essential test management and planning. The presentation covered topics such as test levels, test methodologies, test planning, and test documentation like the master test plan. It emphasized treating testing as a lifecycle process integrated throughout development.
The document provides an overview of software testing methods and concepts. It defines software testing as verifying and validating software to check for errors and ensure it meets requirements. The document discusses different testing methods like static testing (reviews, inspections) and dynamic testing (executing code with test cases). It also defines key terms like verification, validation, defects, bugs, and differences between quality assurance (planning processes) and quality control (product verification).
This document provides an overview of the ISTQB CTAL Test Manager certification. It discusses key topics that will be covered on the exam, including test processes and tools, testing in the software development life cycle, test planning, test control, and assessing development and test processes. The author aims to present 90% of the information directly from the ISTQB syllabus and provides some of their own insights. References and resources are also included to aid further study.
The document provides details about preparing a test plan, including defining the scope, approach, resources, schedule, and activities for intended test activities. It discusses analyzing the product, developing a test strategy, defining objectives and criteria, planning resources and the test environment, scheduling, and identifying test deliverables. Test plans can be master plans, level-specific plans, or type-specific plans. The document also provides guidelines for test plans, including making the plan concise and specific, using lists and tables, and updating the plan regularly. It discusses deciding the test approach, setting criteria, identifying responsibilities, and planning staff training and resource requirements.
This document discusses defect management. It defines a defect as an error or bug in software. Defects can arise during various stages of development due to issues like miscommunication, unrealistic schedules, lack of experience, or poor testing. Defects are classified by severity, work product, type of error, and status. The defect life cycle and management process are also described, including techniques for preventing, discovering, resolving, and closing defects through activities like reviews, logging, analysis, and process improvements.
The document discusses software testing objectives, principles, techniques and processes. It covers black-box and white-box testing, unit and integration testing, and challenges of object-oriented testing. Testing aims to find bugs but can never prove their absence. Exhaustive testing is impossible so testing must be planned and systematic. Frameworks like xUnit can help automate unit testing.
5WCSQ(CFP) - Quality Improvement by the Real-Time Detection of the ProblemsTakanori Suzuki
The document discusses a method called "Development Forecast" for improving software quality through real-time analysis. It evaluates the relationship between results from static code analysis tools and subsequent testing results on a software project. The analysis found violations identified through static analysis correlated with defects found later in integration and release testing, suggesting static analysis can help identify quality risks early. The method is proposed as an effective way to prevent project failures by providing continuous feedback to address risks.
Types of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating system
This document contains the resume of Nataraj Krishnaswamy. It summarizes his professional experience of 12 years in the IT industry as a Scrum Master and in project management roles using both Agile and Waterfall methodologies. He has worked on multiple projects for clients in telecom, insurance, entertainment and aerospace industries. Currently he is working as a Scrum Master for a telecom client at Accenture.
5WCSQ - Quality Improvement by the Real-Time Detection of the ProblemsTakanori Suzuki
1. The document discusses quality improvement in software development projects through real-time detection of problems. It describes current high failure rates in projects and how quantitative management can help.
2. It introduces the "Development ForeCast" approach which uses automated measurements, monitoring, and analysis of source code metrics to detect quality problems in real-time. This allows risks to be identified early.
3. Case studies show how static code analysis tools can evaluate quality at different stages of development, like identifying modules likely to have defects during testing. Real-time monitoring of metrics can improve quality while reducing costs.
The document provides an introduction to software testing fundamentals and artifacts. It discusses test cases, test specifications, test planning, and test execution. Test cases are defined as a set of test inputs, execution conditions, and expected results to test a specific objective. Good test cases should be reasonable, exercise areas of interest, and make failures obvious. The document outlines steps for creating test cases such as breaking the application into testable modules, writing checklists, adding questions, and getting reviews from other testers and developers.
This document provides an overview and introduction to software testing for beginners. It discusses what software testing is, why it's important, and what testers do. Some key points covered include:
- The goal of testing is to find bugs early and ensure quality by designing and executing test cases that cover functionality, security, databases, and user interfaces.
- A good tester has skills like communication, organization, troubleshooting, and being methodical and objective in their work.
- Testing occurs at all stages of the software development life cycle from initial specifications through coding, testing, deployment and maintenance.
This document summarizes Rex Black's book on risk-based testing strategies. It discusses:
- The two main types of risks in testing: product risks related to quality, and project risks related to management and schedules.
- How risk-based testing guides testing activities based on identified risks, prioritizing higher-risk items and allocating more testing effort to them.
- The benefits of risk-based testing over requirements-based testing, like having a more predictable reduction in risk over time and the ability to intelligently reduce testing if needed.
- The history of risk-based testing strategies dating back to the 1980s, and how modern approaches aim to systematically analyze and address risks.
The document discusses software testing concepts and processes. It covers definitions of testing, objectives of testing, types of defects and their costs. It also describes the typical software testing process which includes test planning, preparation, execution, reporting and defect tracking. Additionally, it discusses test strategies such as unit testing, integration testing, system testing and acceptance testing. The overall purpose is to provide an introduction and overview of basic software testing concepts.
Agile/Scrum best Practices to improve quality.If some testing finds some defects, lot of testing would find lot of defects and improve quality. This presentation talks about few testing best practices that an agile team should follow for quality PI.
This document discusses exploratory testing and defines it as "Any testing to the extent that the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests." It describes how all testers do some exploratory testing. Exploratory testers rely on a variety of knowledge, including knowledge of specific domains, risks, and testing techniques. Exploratory testing can differ based on a tester's personality and experiences. Questioning strategies like the Phoenix Checklist can help exploratory testers generate effective questions to test software.
Christian Ramírez presented on software testing considerations for mobile banking applications. Key points included separating test logic from technical drivers, using test automation frameworks, and adopting test design approaches like TDD and BDD. Best practices involved continuous integration, model-based testing, and leveraging tools for code analysis and cross-browser testing. The presentation provided guidance on effective strategies for testing mobile apps across different platforms and environments.
Sharad is a senior software engineer with over 4 years of experience in testing medical devices. He has extensive experience in both automation and manual testing as well as developing automation frameworks using LabVIEW. His resume highlights 3 projects with clients Physio Control and Animas Corporation where he performed roles such as developing automated test equipment, verifying software requirements, and ensuring medical devices received regulatory approval. He is proficient in languages like LabVIEW, operating systems like Windows, and testing skills including requirements analysis and defect tracking tools.
This document discusses innovations and adaptations in agile testing. It covers agile testing roles and practices like testing early and often, automating tests, and continuous integration. It discusses challenges like testing exploratory and non-functional requirements within sprints. One approach presented is to test these in parallel with a sprint lag through dedicated test phases. This reduces risks of critical defects found late impacting releases. The document also discusses adaptations like managing test environments, skills development, and indicators to optimize agile testing.
Objectives:
1. To understand software testing and its importance.
2. To understand the concepts of software quality.
3. To see the different classes/ levels/ types of testing.
4. To see the different test case design techniques.
5. To understand the software processes related to testing in a typical software organisation.
Rick Craig, a consultant with over 30 years of experience in testing and test management, presented a training on essential test management and planning. The presentation covered topics such as test levels, test methodologies, test planning, and test documentation like the master test plan. It emphasized treating testing as a lifecycle process integrated throughout development.
The document provides an overview of software testing methods and concepts. It defines software testing as verifying and validating software to check for errors and ensure it meets requirements. The document discusses different testing methods like static testing (reviews, inspections) and dynamic testing (executing code with test cases). It also defines key terms like verification, validation, defects, bugs, and differences between quality assurance (planning processes) and quality control (product verification).
This document provides an overview of the ISTQB CTAL Test Manager certification. It discusses key topics that will be covered on the exam, including test processes and tools, testing in the software development life cycle, test planning, test control, and assessing development and test processes. The author aims to present 90% of the information directly from the ISTQB syllabus and provides some of their own insights. References and resources are also included to aid further study.
The document provides details about preparing a test plan, including defining the scope, approach, resources, schedule, and activities for intended test activities. It discusses analyzing the product, developing a test strategy, defining objectives and criteria, planning resources and the test environment, scheduling, and identifying test deliverables. Test plans can be master plans, level-specific plans, or type-specific plans. The document also provides guidelines for test plans, including making the plan concise and specific, using lists and tables, and updating the plan regularly. It discusses deciding the test approach, setting criteria, identifying responsibilities, and planning staff training and resource requirements.
This document discusses defect management. It defines a defect as an error or bug in software. Defects can arise during various stages of development due to issues like miscommunication, unrealistic schedules, lack of experience, or poor testing. Defects are classified by severity, work product, type of error, and status. The defect life cycle and management process are also described, including techniques for preventing, discovering, resolving, and closing defects through activities like reviews, logging, analysis, and process improvements.
The document discusses software testing objectives, principles, techniques and processes. It covers black-box and white-box testing, unit and integration testing, and challenges of object-oriented testing. Testing aims to find bugs but can never prove their absence. Exhaustive testing is impossible so testing must be planned and systematic. Frameworks like xUnit can help automate unit testing.
5WCSQ(CFP) - Quality Improvement by the Real-Time Detection of the ProblemsTakanori Suzuki
The document discusses a method called "Development Forecast" for improving software quality through real-time analysis. It evaluates the relationship between results from static code analysis tools and subsequent testing results on a software project. The analysis found violations identified through static analysis correlated with defects found later in integration and release testing, suggesting static analysis can help identify quality risks early. The method is proposed as an effective way to prevent project failures by providing continuous feedback to address risks.
Types of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating systemTypes of operating system
This document contains the resume of Nataraj Krishnaswamy. It summarizes his professional experience of 12 years in the IT industry as a Scrum Master and in project management roles using both Agile and Waterfall methodologies. He has worked on multiple projects for clients in telecom, insurance, entertainment and aerospace industries. Currently he is working as a Scrum Master for a telecom client at Accenture.
- Prasanth Kumar Pendam has over 9.5 years of experience in manual testing including team leading activities. He has strong experience in test planning, test case design, and working with tools like CA Clarity PPM and HP Service Manager.
- He is proficient in various phases of the software development life cycle including requirements analysis, testing, documentation, and deployment testing.
- He has worked on several projects as a technology lead and senior test engineer, with responsibilities including requirement gathering, test case preparation, automation, and issue tracking.
Shaista Fatima has over 3.6 years of experience in automation and manual testing using Selenium and Jenkins. She has expertise in test case design, execution, and reporting for regression, sanity, and exploratory testing. She is proficient in languages like Java, C#, and tools like Selenium, Jenkins, Maven, and SQL Server. She has worked on projects in domains like IT, telecom, and healthcare and aims to contribute to testing efforts through test automation, documentation, and communication.
This document provides details about Sunetra Banerjee's professional experience as a Senior IT QA Lead. It outlines her roles and responsibilities in various projects at different organizations, including Clinical Ink, Travelers-Canada, InteraXon, Vecna Technologies, Cavalier IT, and Cognizant Technology Solutions. The document highlights her experience leading testing teams, creating testing artifacts, defect tracking, and ensuring quality assurance. It also lists her technical skills and certifications in software testing.
Sunetra Banerjee has over 10 years of experience in software QA testing and development. She has worked as a Senior QA Lead for multiple companies, leading teams of up to 15 people across various projects. Her experience includes testing web, mobile, and mainframe applications across different platforms and programming languages. She is proficient in defect tracking, test case management, and agile methodologies. Currently she works as a Senior QA Engineer and Lead at Clinical Ink, testing their mobile and web applications.
This document contains the resume of Sunetra Banerjee, detailing her experience as a Senior IT QA Lead and Software QA Engineer. She has over 10 years of experience in software testing and quality assurance. Currently she works as a Senior QA Engineer and Lead at Clinical Ink, where she is responsible for testing mobile and web applications and leading a team through the product release cycle. Previously she has worked as a QA Lead at Travelers-Canada and InteraXon Inc., and as a QA Engineer at Vecna Technologies and Cavalier IT, where she tested various software applications and led teams through the QA process.
This document contains the resume of Sunetra Banerjee, which includes details about her professional experience, qualifications, and skills. She has over 10 years of experience in software QA testing and leading projects of up to 15 team members. Her areas of expertise include agile methodologies, mobile app testing, database testing, and automation testing. She is proficient with various project management and defect tracking tools. Currently she works as a Senior QA Engineer and Lead at Clinical Ink, where she is responsible for testing mobile and web applications and leading the QA team.
This document contains the resume of Sunetra Banerjee, who has over 10 years of experience in software QA testing and development. She has led projects with teams of up to 15 members. Her experience includes testing web, mobile, and mainframe applications across various industries. She is proficient in testing methodologies, defect tracking, and automation tools.
Shivam Chhatwal is seeking a position where he can contribute to an organization's progress and success. He has over 1 year of experience as a Software Quality Assurance Tester at Elcom Innovations Ltd. His skills include testing software through all phases of the SDLC, testing protocols like SIP and SNMP, and tools like MySQL, Wireshark, and Redmine. He is proficient in Windows, Linux, and databases. His projects have involved testing embedded systems kernels, VoIP field telephones, and network management systems. He creates test cases, plans and executes tests, and manages defects. Shivam holds a B.Tech in Computer Science and has completed training in software testing, methodologies,
Arunkumar Muthusamy is a Quality Assurance/Technical/Test Manager with over 10 years of experience in test management and product testing. He has extensive experience testing networking and video streaming products from Cisco, Proximus, and Konica Minolta. Some of his responsibilities include test planning, requirement analysis, automation testing, defect management, and ensuring quality product delivery. He is proficient in test methodologies like Agile and Scrum, as well as various testing tools and techniques including performance, security, and automation testing.
Software Test Engineer with 3.6 years of experiencevijaya lakshmi
Vijaya Lakshmi has over 3.6 years of experience in software testing and quality assurance. She has worked as a senior software test engineer and test engineer for various companies testing applications in domains such as product lifecycle management, insurance, and administration tools. She has experience in all phases of testing including requirements analysis, test case design, execution, defect tracking, and reporting. Vijaya Lakshmi is proficient in testing methodologies, tools, and programming languages. She is looking for new opportunities as a QA/test engineer.
This resume summarizes Pawan Kumar's qualifications and experience as a software tester. He has 2 years of experience as an automation tester using tools like Selenium, QTP, and SoapUI. He has expertise in test automation, manual testing, defect tracking, and working in agile environments. Some of Pawan's projects include testing insurance and banking applications for Disney and Darden Restaurants.
Sunetra Banerjee has over 10 years of experience in software QA testing and development. She has led testing teams of up to 15 members across multiple projects. Her experience includes testing web, mobile, and mainframe applications using Agile and Waterfall methodologies. She is proficient in test planning, defect tracking, automation, and creating test reports.
The document provides a summary of Jaswinder Kaur's professional experience as a Verification and Validation Lead with over 11 years of experience in software testing. She has extensive experience working with cross-functional teams on healthcare applications. Her responsibilities have included test planning, authoring validation documents, defect management, and ensuring regulatory compliance. She is proficient with testing tools like ALM, QTP and has experience working in Agile environments.
Sunetra Banerjee is a senior IT QA lead with over 10 years of experience in software testing and development. She has led project teams of up to 15 members across various projects in healthcare, insurance, and other industries. Her experience includes testing web, mobile, and mainframe applications using Agile and waterfall methodologies. She is proficient in defect tracking, test automation, and coordinating onsite and offshore teams.
Rajesh Joshi has over 12 years of experience as a manual software tester. He currently works as a Project Lead at Capgemini managing multiple international testing projects. Prior to Capgemini, he worked on testing projects in various domains including energy and utilities, publishing, and telecommunications.
Rajakumari Thota has over 9 years of experience in software testing. She has expertise in test automation using tools like Selenium, Appium, and JMeter. She has extensive experience testing web and mobile applications, including writing test cases and executing automation test suites. She has worked on projects across various domains and platforms, including testing Android and iOS applications. She is proficient in functional and non-functional testing methodologies.
Sonali Sengupta is a software tester with over 10 years of experience testing Java and SharePoint applications. She is seeking new opportunities to apply her analytical and testing skills. She has extensive experience in test planning, execution, automation, and defect management. She is proficient in Selenium, SQL, and several testing tools. Her most recent role involves testing SharePoint applications for Aviva as a test analyst.
Saurabh Jain is seeking assignments as a manual tester with over 3 years of experience in functional testing, writing test cases and scripts, and executing tests using Quality Centre and QTP. He has experience testing various software products and modules like SAP FICO and Planning and Forecasting. His skills include creating test cases, executing tests, setting up test environments, tracking defects, and preparing test reports. He is proficient in Quality Centre, QTP, and testing web and SAP applications.
1. K S Mary Deepthy
Mobile: Primary – 09740060263
Email: marydeepthy@gmail.com Alternate Contact – 09980741602
Professional Synopsis
A technology driven professional with 10 years of experience in Testing, Test planning &
designing test strategies which will output high quality releases with zero field issues
Currently working as Senior Technical Lead in UST Global.
Experience in Leading ,Mentoring and Managing a big team(One of the two leads for a team of
36 people)
Experience in setting up the Test procedures including the Test Plan & Test Design for customer
acceptance and product launch
Worked with cross location and cross functional teams including developers and testers and
created test assets that helps in delivering the product with high test quality
Proven expertise in communicating efficiently within the team and leading them to achieve
project milestones
Experience in planning, scheduling, managing and assigning the testing activities for the
engineers on a day to day basis
Experience in analyzing the logs for the defects and identifying the root cause, and giving the
first level analysis
Familiar with Agile methodologies(Scrum)
Expertise in Project planning & estimation
Protocol test experience for Bluetooth and WiFi.
Exposure to QA testing methodologies viz functional, regression and smoke testing
Expertise in Black box test techniques & methodologies
Expertise in C programming
Handled Interoperability Testing for various Bluetooth devices and platforms
Hands on experience with Android, iPhone, Windows and Symbian handsets.
Familiar with configuring Wireless access points
Expertise in White Box Testing which include code analysis and API testing
Experience in testing inside RF lab under tight security conditions
Onsite experience with Texas Instruments, Israel and Samsung Electronics, South Korea
Experience
1) UST Global Pvt. Ltd, Bangalore
Designation : Senior Test Analyst
Duration : 2011 July - Till present
Emp Code : U27902
2) Nokia India Pvt. Ltd, Bangalore
Designation : Test Engineer
Duration : 2008 February- Till 2011 July
Emp Code : 10283498
3)Samsung India Software Operations, Bangalore
Designation : Senior Software Engineer
Duration : 2007 January- 2008 February
2. Emp Code : 1566
4) Sasken Communications, Bangalore
(Consultant atTexas Instruments Israel Ltd. )
Designation : Software Engineer
Duration : 2006 May -2007 January
Emp Code : 60240
5) Avenir Computer Services, Cochin
Designation : Member Technical Staff
Duration : 2004 September- 2006 May
Education
MCA from MACFAST, Tiruvalla, M. G University in 2004. (Secured 86%)
BSc (Physics) from St. Joseph’s College, Alappuzha, Kerala University in 2000. (Secured 94%)
Pre-Degree from St. Joseph’s College, Alappuzha, KeralaUniversity in 1997. (Secured 69%)
SSLC from Mary Immaculate HS, Alappuzha, KeralaState Board in 1995. (Secured 84%)
Core Competencies
Operating System : Windows 98, 2000, Android, Chrome
Languages and Libraries : C
Packages & Tools : Clear Case, Trace 32,
FTS4BT Air Sniffer, Quality Center (HP QC), Rational Change,
Clear Quest, Rational Team Concert (RTC), JIRA, JAMA
(Contour)
Organizational Experience
Key Projects Handled
1) Team Lead- Chrome Auto Test Automation (Ongoing)
Role: Team Lead
Team Size : 8
Scope: Test content automation for Intel next generation platforms (designed for Google
Chromebook) on Chrome Operating System
My Achievements in this project:
1. Not a planned project- I have taken up the initiative to automate the test cases
2. Actively involved in the discussion with client and succeeded in getting the project
for UST Global
3. Identified people from the manual testing team and got them trained for python
automation
4. Recruited people experienced in python who can also train other members
3. Roles and Responsibilities:
Lead the team in creating the test plan using Software requirement Specification,
review the test cases when created
Analyzing and identifying automation candidates from the test plan.
Recruit team members, provide technical assistance when required by arranging
trainings and resources
Conduct daily scrum and update the automation status on a daily basis to higher-ups.
Provide a friendly atmosphere to the team by encouraging and motivating them
2) Validation Lead – Google Chromebook
Team Size : 34
Scope : Test Content development and platform validation for Next generation
Intel Platforms (designed for Google Chromebook) on Chrome Operating System.
My Achievements in this project:
1. The project was in the initial stage when I joined. I lead the team in creating the
complete test plan from scratch
2. Actively involved in shortlisting and recruiting candidates- this was done in a record
time- all the candidates were on-boarded in less than a month.
3. I have taken initiative in creating a task force to review the test plan, which
consisted of around 10,000 test cases and optimized and reduced the count to 2250.
4. I have created new test cases in each module which will unmask hidden errors. The
test plans have helped in identifying critical bugs well in advance
5. Created Bug Format and trained the team in how to file a bug effectively
6. Trained the team on technologies like Bluetooth and Wi-Fi
7. All the testing activities were tracked using excel sheets – I have taken up the
initiative to talk to customer and involve test tools such as Contour and HP QC so
that book keeping and reporting will be error free, organized and easily accessible
8. Formed a taskforce to upload all the requirements to Contour and test cases to QC.
9. Trained all 34 members of the team in Contour and HP QC and completely migrated
the project to QC and contour
10. Rational Team Concert was introduced to the team and I trained the team in how to
use RTC
11. I introduc ed “Daily Individual goals” when the team was struggling to meet deadlines
and this was a success
12. Introduced scrum and daily stand-ups to the team
13. Awarded the “top performer” award c onsidering the above ac tivities
Roles and Responsibilities:
Create and design test plan from requirement specification
Create test set ups.
Lead the team in validation, assign tasks on a daily basis
4. Review the bugs before filing
Guide the team to complete the test cycle for each build and decide the execution
pattern when interim builds are released
Create execution and bug reports and share them with stake holders on a daily basis
Attend Global Scrum meetings and get updates on the project and share them with
the team
Conduct daily scrum and update the status on a daily basis to higher-ups.
Provide technical assistance to team
3) Validation Lead / Individual contributor - Validation for Tablet Phone
Team Size : 6
Scope: Member of Test validation team for testing Bluetooth, NFC and Wi-Fi modules on
the next generation Intel platforms working on Android Operating System. The tests are
performed on factors such as security vulnerability, range, transfer speed, and reliability of
operation.
My Achievements in this project:
1. I was the first member to join this project. It was me who created all the test plans, test set
ups, test procedures, lab set up (including identifying and ordering test support devices )
2. Created the report format for the daily execution.
3. Documented all the test set ups and procedures for future use.
4. Received appreciation from the client many a times for going through the logs and providing
accurate analysis whenever a bug is found.
5. Created the security vulnerability test plan, and used backtrack as the test tool after doing
research.
6. Trained other members of the team in executing day to day tasks.
Roles and Responsibilities:
Gap analysis on the test coverage of existing test cases
Creating test plans, test set ups and automating test cases using existing in-house
framework
Executing the test cases for Bluetooth, Wi-Fi and NFC modules
Testing Interoperability against different platforms.
Day to day interaction with development team, providing logs for errors found, test
methods to follow and retesting when fix is available.
Do the first levels debug for the failures and log the facets in the defect tracking tool
2) Individual Contributor - Test Engineering for Nokia Mobiles (Symbian Production Branch)
Team Size : 10
Scope: Member of Test Engineering team for Nokia handsets in the Symbian production
branch. The team was involved in study of new features, testing, bug reporting & tracking and
publishing reports.
5. My Achievements in this project:
1. Taken the responsibility of individual products, followed the errors reported by the mobile
phone users in public forums and have taken them to the proper teams.
2. Critical bugs were found before the release, which could have cost fatal if went to production
unnoticed.
3. Helped in solving some critical internal setup issue (issue was related to Nokia Software
updater) which was causing huge delay in the test efforts. Voluntarily documented the issue
reasons and solutions and shared the same among team which helped many people across the
globe to solve the issue
4. Received appreciation for documenting all the test procedures and sharing it across the team.
I have also received appreciation for taking up testing tasks which require lots of time,
patience and effort.
Roles and Responsibilities:
Managing subcontractors who does the functional testing, collecting reports from them, do
review and analysis of the results, comparing with previous cycles and then publishing the
report to stake holders
Attending in Software Content Board (which decides the test focus, NFT & ET areas for
each software release), Content Control Board(which decides the New Requirement areas to
be taken for each release ) and Incident Review Board(which decides on action points for
bugs reported, decides bug priority and status)
Execution of test sets for weekly releases, reporting bugs with prioritization
arguments, uploading crash files, preparing & publishing test report
Creating BAT, focus & new requirement test set for weekly release and sharing them
with the subcontractors for execution
Execution of sales test activities, preparing & publishing sales test report
Reporting the bugs found in Rational Change and giving prioritization arguments
Bug status follow up with build & integration teams, providing screenshots and traces
when necessary
Verification of errors
4) ISA Releasing- Developing Test application For Core Software
Team Size : 4
Role : Team Member / Individual Contributor
Scope: The project deals with developing test applications to test various servers in S40
platforms. Test applications are then delivered to various testing teams.
My Achievements in this project:
1. This project was in C# which was a new language for me, but I have managed to finish the
project well within the allotted time slot
2. One of the helper modules which we used had a bug and created lots of crashes when the test
cases were executed. The module was no longer supported by the team who developed that. I
have taken up the task voluntarily, as a challenge, and then re-wrote the complete module.
6. The new module was then shared globally across teams who were using the older one. This
module was faster and efficient.
3. Voluntarily created a test suite for API testing
Roles and Responsibilities:
1. Actively participating in discussions with customers
2. Design and develop the applications for various teams
3. Implement test suite to test (API testing) the applications developed
4. Carry out the testing and debugging
6) Samsung Handset Testing
Team Size: 3
Role: Team Member
Platform: Samsung Mobile Platform
Scope: Testing Samsung handsets for IRDA, and Bluetooth profiles. Test cases were prepared
based on client requirement and guide lines.
My Achievements in this project:
1. Taken trainings in Bluetooth technology for the team in Samsung
2. Prepared a design document for implementing JSR 82
3. Taken trainings for the team on JNI
4. Taken up the initiative to introduce and use Trace 32 to identify the root cause for bugs
Roles and Responsibilities:
1. Creating test plans from the design documents
2. Actively participating in discussions with development team
3. Preparing API test plan and executing the test cases,
4. Collecting logs and crash dumps and helping developer to reproduce and fix the bug.
7) Interoperability Testing
Company: Texas Instruments Israel
Team Size: 2
Role: Team Member
Technologies: Bluetooth
Scope: The project included Creating & Executing test cases for Bluetooth profiles on embedded
platforms. Test cases were created to see that all Bluetooth features available in the device under
test are interoperable with other Bluetooth devices available in market.
Roles and Responsibilities:
1. Involved in studying Bluetooth profile specification
2. creating test requirements and test plans
3. Execution the test cases on various Bluetooth devices and mobile platforms
4. Creating reports using test Director
5. Raising bug report in clear quest and classifying them according to the priority.
7. My Achievements in this project:
1. This was a new project for Sasken from TI and I was part of the team who set up the lab in
the TI ODC in Sasken.
2. Helped in creating the test plans and added the test plans in to Test Director (now Quality
Center).This was a task which required lots of time and effort.
3. Trained the team members in Bluetooth by giving them regular presentations. Documents
were prepared on Bluetooth and the same was circulated in the team.
9) API testing - BIP & OPP
Company: Avenir Computer Services, Cochin
Team Size: 2
Role: Team Member
Technologies: Bluetooth, Windows 2000, C
Scope: The project involved Testing of basic Bluetooth profiles basically like OPP and BIP.
Test Suite was created to test the basic functionalities of the APIs that are exposed.
Roles and Responsibilities:
1. Understanding Bluetooth specification for the corresponding profile
2. Preparing a test plan from the specification
3. Implementing the API test suite
4. Conducting API testing for the profiles
My Achievements in this project:
1. This was my first technical assignment after graduation. I have learned the specifications
thoroughly and then prepared the API test plans using the specifications from the Bluetooth
SIG website and also the chm documents of the application.
2. I have created test suites in java and C which is being re-used by the company for testing
other Bluetooth profiles.
3. Voluntarily learned java Native Interface and successfully written a wrapper application to port
the APIs from C interface to Java.
Personal Details
Contact Address : Flat No. 402, Shreevari Mansion,
Kemapanna Main Road,
Vignan Nagar, Bangalore
Date of Birth : 27th Apr’1980
Marital Status : Married