The document discusses software quality assurance and testing. It describes the software development life cycle, which includes stages like information gathering, analysis, design, coding, testing and maintenance. It then provides details about various testing techniques like black box testing, white box testing, unit testing, integration testing, system testing and user acceptance testing. It also discusses testing documents like test plan, test cases, defect report and test summary report.
Nitesh.M is seeking a position as a Software Test Engineer. He has undergone training in software testing and has skills in manual testing, SQL, web service testing, and defect tracking tools. Some of his testing experience includes writing test cases for an time-tracking application, performing compatibility testing on travel websites, and developing an academic project using a PIR sensor for security control. He has a Bachelor's degree in Instrumentation Engineering and proficiency in technologies like Oracle and Bugzilla. His hobbies include sports like badminton and cricket.
Shashank Kale has over 6 years of experience in software testing and quality assurance. He has worked as a test engineer for several companies in banking, finance, and insurance. Some of his responsibilities include preparing and executing test cases, performing both manual and automation testing, and reporting on defects. He has expertise in testing web, desktop, and mobile applications using tools like QC, JIRA, and SQL.
V.V. Kumar is seeking a challenging career applying his interpersonal and technical skills in software. He has strong knowledge of both manual and automation testing, SDLC and STLC processes. He is proficient with test management tools like QC and TD, and has experience with QTP, VB scripting, test planning and review processes. He has a Bachelor's degree in EEE and skills in programming languages like C/C++ and Java as well as Windows, Unix and scripting languages like VB.
Venkataramana Reddy is seeking a position as a Software Functional Testing Engineer. He has a B.Tech from Jawaharlal Nehru Technological University with over 70% and 4 months of testing tools training from LiveTech, Hyderabad. His training included manual and automation testing using tools like HP QTP and HP QC. He has experience in test case design, execution, defect reporting, and functional, compatibility and regression testing. His skills include VB Script, C, SQL, HP QTP, HP QC, Bugzilla and Windows. He has worked on the WBMS project at LiveTech performing test case preparation, execution, and defect reporting using Bugzilla and Track+ for
Vurukuti Narasinga Rao is a QA Analyst with over 4 years of experience in manual and automated software testing. He has worked on projects for clients such as American Express, Mass Mutual Life Insurance, and Travelers testing web applications, APIs, and legacy systems. Narasinga is proficient in test planning, execution, defect tracking, and has experience using tools such as ALM, QC, QTP, SoapUI, and Selenium. He is ISTQB certified and currently works as a Quality Analyst for Cognizant in Hyderabad, India.
Vivek D is a software tester with over 2 years of experience in manual testing. He has expertise in system testing, regression testing, unit testing, ad-hoc testing, and bug tracking using Bugzilla. He is ISTQB certified and has experience in test case design, requirement analysis, defect reporting, and Agile methodologies like Scrum. Currently he works as a manual tester for TT Network Integration India Pvt Ltd on their Telematics vehicle tracking application project.
Pankaj Tiwari is seeking a challenging position as a testing engineer specializing in front end and back end testing using manual and automation testing techniques. He has over 3 years of experience in software testing including mobile app testing for iOS and Android. Some of his experience includes usability testing, regression testing, test case design, and bug reporting using tools like JIRA. He has worked on projects for clients in the US, Australia, and Ukraine testing a variety of web and mobile applications.
This resume summarizes Ravinder's experience as a senior test engineer with over 5 years of experience in manual and automation testing. He has extensive experience in test frameworks like Selenium, UFT, and tools like JIRA. His areas of expertise include functional, regression, API and cross-browser testing. He has worked on projects in various domains for clients like Microsoft, Infosys and Unum.
I am having rich experience in Automation Testing using HP UFT, HP ALM, TFS, MTM (Microsoft Test Manager), JIRA, Jenkins, Test Link and RPA tool - Blue Prism
Have good knowledge of ITIL foundation training.
And also having good exposure of providing Trainings.
• 5.3 years of experience in Software Testing (Functional Testing).
• 1.8 years of client onsite experience in Waltham, MA USA.
• Worked with Banking domain clients like JP Morgan Banking group (4 years’ experience)
• Excellent QA experience in all phases of Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC).
• Good Experience and Knowledge in different project management models like waterfall and Agile Scrum.
• Expertise in Functional, Integration, Regression, SIT, Black Box and User Acceptance Testing (UAT).
• Extensive experience in creating Testing milestones like Test Plans, Test Scenarios, Test Strategies, Test Cases, Test Reports and RTMs.
• Played different roles – as Scrum Master, QA Lead, Senior Tester, SME, BA etc.
• Worked on – Requirement analysis, Test Condition preparation, Test script Creation in Manual & BPT format, Test Execution, Defect life cycle workflow, Performance testing etc.
• Business Analyst experience in working closely with product partners, defining requirements, creating design documents and interface diagrams.
• Dedicated, conscientious individual with strong sense of responsibility, work flexibility and adaptation to changing environments professionally and personally.
DRB EXP RESUME manual and selenium master copy corrected 2
Dikhit Ranjan Behera has over 2 years of experience in information technology, including 1 year of experience with automation testing using Selenium. He has skills in manual testing, automation testing with Selenium and TestNG, defect tracking with tools like HPQC and Jira, and programming languages like Java. He currently works as an Associate Software Engineer at Mphasis Limited, where he has been involved in testing projects including an asset management system and a healthcare application.
Altaf Lakhani is an experienced software tester with over 3 years of experience testing web and client-server applications in various industries. He has extensive experience with manual and automation testing using Selenium WebDriver, SQL queries, and tools like Jira. His most recent role was as a QA Automation Tester at A-Z Wholesale in Dallas, where he automated test cases using Selenium and participated in Agile ceremonies. He has experience developing test plans, executing test cases, and documenting defects.
The document provides a professional synopsis for an individual with 3 years of experience in software testing. It summarizes their experience in various testing types such as functional, regression, scenarios, and database testing. It also lists the tools used like Selenium, Bugzilla, and TestNG framework. Finally, it outlines 3 projects the individual worked on, including their roles of preparing and executing test cases, identifying defects, and automation testing using Selenium.
This resume summarizes Chenchaiah Challa's qualifications and experience as a software tester. He has a B.Tech in Electrical and Electronic Engineering from Jawaharlal Nehru Technological University. He underwent 4 months of testing training at LiveTech, Hyderabad where he learned to understand requirements, design test cases, and perform functionality, compatibility, and regression testing. He has experience using testing tools like QTP and defect tracking tools like Bugzilla and TestLink. His most recent project involved testing an insurance application at LiveTech where he created test scripts and cases, performed black box and regression testing, and reported defects.
This document summarizes the skills and experience of Jenifer Breeze. She has over 3 years of experience in software development and testing. She has expertise in web application development using Java technologies and databases like Oracle and MySQL. She is proficient in development, manual testing, automation testing, ETL, and database testing. She has worked on projects for clients in various domains and roles including senior tester, tester, and software developer. Her skills include preparing documentation, developing test cases, unit testing, and ensuring quality.
- Vishwanath G Teli is seeking a position that allows him to utilize his skills in manual testing, Java, SQL and continuous self-development.
- He has over 2 years of experience in software testing and has worked on projects for Hindustan Unilever Ltd. testing tools like NetSuite and GChaRM.
- His responsibilities have included requirement collection, test case design, defect logging, regression testing and creating test reports.
Yogeshwaran has over 5 years of experience in manual and automation software testing using Selenium with Java. He currently works as a QA Analyst at Oracle India and has previous experience working as a Software Engineer at CGI. Some of his key skills include Selenium, JUnit, MySQL, ALM, JIRA, and Oracle Test Manager. He has experience testing projects in domains such as project management, energy/utilities, and machine-to-machine. Notable past projects include testing Primavera P6 Professional Project Management software and the UK's DCC smart meter system. He holds a B.E. in computer science and is ITIL certified.
This document provides an overview of software testing concepts related to manual testing. It discusses key topics like software quality, software quality assurance, software quality control, requirements gathering, design, programming, integration testing, system testing, and more. The document is intended to educate readers on software testing processes and techniques.
The document discusses key concepts in software testing including software quality, software quality assurance (SQA), software quality control (SQC), and the V-Model. It describes the software development lifecycle including requirements gathering, design, coding, testing, and maintenance. It provides details on different types of testing like unit testing, integration testing, system testing, and reviews/inspections conducted at various stages. Key testing techniques mentioned are black box testing, white box testing, basis path testing, control structure testing, and mutation testing. The V-Model mapping development stages to corresponding testing stages is also explained.
The document discusses various stages in the software development life cycle (SDLC) including reviews, testing, and maintenance. It describes reviews that take place during analysis and design to verify requirements and design documents. Unit testing involves testing individual programs using techniques like basic path coverage. Integration testing combines programs to test interfaces. System testing is conducted by a separate team and includes usability, functional, and non-functional testing. User acceptance testing collects customer feedback. Maintenance involves addressing change requests and improving testing processes. The "V" model is presented as an extension of the traditional waterfall SDLC model.
This document provides an overview of software testing concepts for beginner software testers. It discusses key concepts like software quality assurance, software quality control, requirements gathering, reviews, design, programming, testing techniques like black box testing and white box testing, integration testing, system testing, user acceptance testing, and release and maintenance. Testing responsibilities are mapped to different phases and techniques that testing teams can use to verify and validate the software.
This document provides an overview of software testing concepts for beginner software testers. It discusses key concepts like software quality assurance, software quality control, requirements gathering, reviews, design, programming, testing techniques like black box testing and white box testing, integration testing, system testing, user acceptance testing, and release and maintenance. Testing responsibilities are mapped to different phases and techniques that testing teams can use at each phase like walkthroughs, inspections, and regression testing. The document aims to give beginners a comprehensive understanding of the software testing process.
The document discusses the Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC). It describes the various phases of SDLC like requirements gathering, analysis, design, coding, testing, and deployment. It then explains the stages of STLC in more detail - requirements analysis, test planning, test case development, environment setup, test execution, and test closure. Finally, it provides definitions related to the bug life cycle and its flow chart.
The document discusses various aspects of software development including:
1. Software quality focuses on meeting customer requirements and expectations in terms of functionality, performance, cost and time to market.
2. Common software development process models include waterfall, prototype, spiral and agile models which are suited for different types of requirements.
3. Testing is a critical part of the development process and includes unit, integration, system and user acceptance testing. System testing involves testing functionality, usability, compatibility and other quality attributes.
This document provides an overview of software testing concepts including the software development life cycle, different testing methodologies, levels of testing, environments, process models, types of testing, and the software testing life cycle. It defines key terms and describes the roles and processes involved in each phase of development and testing. The document is intended as a manual on software testing engineering principles and practices.
The document discusses software testing and the software development life cycle (SDLC). It provides an agenda that covers topics like types of testing, test case design, bug tracking, and SDLC models. The SDLC models discussed include waterfall, V-model, spiral model, and agile development models. The document describes the phases of the waterfall model SDLC such as requirements gathering, analysis, design, coding, testing, and deployment/maintenance.
The document discusses the software development life cycle (SDLC) process. It includes 6 main steps: 1) requirement gathering, 2) software analysis, 3) software design, 4) coding, 5) testing, and 6) implementation. For each step, the document provides details on the objectives and activities involved. It also lists advantages of following the SDLC process such as increased quality, improved tracking, and decreased risks. Finally, it provides a coding example for a basic calculator application to illustrate one step of the process.
The document discusses software testing fundamentals and principles. It defines software testing as evaluating a product to determine if it contains any defects and satisfies requirements. Testing is important to prevent errors and ensure quality, security, efficiency and flexibility. The key goals of testing are to find defects, verify that specifications are properly implemented, and ensure customer expectations are met.
Bhavana Singh is a Testing Engineer with over 2 years of experience in functional, regression, and compatibility testing. She has extensive experience testing mobile apps, websites, and other applications on platforms like iOS, Android, and HTML5. Currently working as a Testing Engineer at GlobalStep Services Pvt. Ltd in Pune, her responsibilities include test case creation, execution, defect reporting, and daily status updates with her Test Lead. She has a B.Tech in Information Technology and is certified in Software Quality Testing from Mind Scripts Technology.
Bhupendra Dhore is seeking a position as a test engineer utilizing his technical skills including Oracle11G, CCNA, Redmine, Jira, manual testing, and core Java. He has a Bachelor's degree in engineering from R.T.M.N.U. and worked as a test engineer at AgreeYa Mobility for over 5 years testing projects including Edvelop and Streben using manual and automated testing. He has also completed projects in embedded systems and autonomous robot navigation.
Akram Khan has over 3 years of experience as a Software Testing Engineer. He has expertise in manual testing, Selenium automation testing, and tools like JIRA. Some of his responsibilities include creating test plans, executing test cases, reporting bugs, and ensuring projects are delivered on time. He has worked on several projects for CORE Centre involving web applications built with technologies like ASP.NET, C#, and SQL Server.
Nitesh.M is seeking a position as a Software Test Engineer. He has undergone training in software testing and has skills in manual testing, SQL, web service testing, and defect tracking tools. Some of his testing experience includes writing test cases for an time-tracking application, performing compatibility testing on travel websites, and developing an academic project using a PIR sensor for security control. He has a Bachelor's degree in Instrumentation Engineering and proficiency in technologies like Oracle and Bugzilla. His hobbies include sports like badminton and cricket.
Shashank Kale has over 6 years of experience in software testing and quality assurance. He has worked as a test engineer for several companies in banking, finance, and insurance. Some of his responsibilities include preparing and executing test cases, performing both manual and automation testing, and reporting on defects. He has expertise in testing web, desktop, and mobile applications using tools like QC, JIRA, and SQL.
V.V. Kumar is seeking a challenging career applying his interpersonal and technical skills in software. He has strong knowledge of both manual and automation testing, SDLC and STLC processes. He is proficient with test management tools like QC and TD, and has experience with QTP, VB scripting, test planning and review processes. He has a Bachelor's degree in EEE and skills in programming languages like C/C++ and Java as well as Windows, Unix and scripting languages like VB.
Venkataramana Reddy is seeking a position as a Software Functional Testing Engineer. He has a B.Tech from Jawaharlal Nehru Technological University with over 70% and 4 months of testing tools training from LiveTech, Hyderabad. His training included manual and automation testing using tools like HP QTP and HP QC. He has experience in test case design, execution, defect reporting, and functional, compatibility and regression testing. His skills include VB Script, C, SQL, HP QTP, HP QC, Bugzilla and Windows. He has worked on the WBMS project at LiveTech performing test case preparation, execution, and defect reporting using Bugzilla and Track+ for
Vurukuti Narasinga Rao is a QA Analyst with over 4 years of experience in manual and automated software testing. He has worked on projects for clients such as American Express, Mass Mutual Life Insurance, and Travelers testing web applications, APIs, and legacy systems. Narasinga is proficient in test planning, execution, defect tracking, and has experience using tools such as ALM, QC, QTP, SoapUI, and Selenium. He is ISTQB certified and currently works as a Quality Analyst for Cognizant in Hyderabad, India.
Vivek D is a software tester with over 2 years of experience in manual testing. He has expertise in system testing, regression testing, unit testing, ad-hoc testing, and bug tracking using Bugzilla. He is ISTQB certified and has experience in test case design, requirement analysis, defect reporting, and Agile methodologies like Scrum. Currently he works as a manual tester for TT Network Integration India Pvt Ltd on their Telematics vehicle tracking application project.
Pankaj Tiwari is seeking a challenging position as a testing engineer specializing in front end and back end testing using manual and automation testing techniques. He has over 3 years of experience in software testing including mobile app testing for iOS and Android. Some of his experience includes usability testing, regression testing, test case design, and bug reporting using tools like JIRA. He has worked on projects for clients in the US, Australia, and Ukraine testing a variety of web and mobile applications.
This resume summarizes Ravinder's experience as a senior test engineer with over 5 years of experience in manual and automation testing. He has extensive experience in test frameworks like Selenium, UFT, and tools like JIRA. His areas of expertise include functional, regression, API and cross-browser testing. He has worked on projects in various domains for clients like Microsoft, Infosys and Unum.
I am having rich experience in Automation Testing using HP UFT, HP ALM, TFS, MTM (Microsoft Test Manager), JIRA, Jenkins, Test Link and RPA tool - Blue Prism
Have good knowledge of ITIL foundation training.
And also having good exposure of providing Trainings.
• 5.3 years of experience in Software Testing (Functional Testing).
• 1.8 years of client onsite experience in Waltham, MA USA.
• Worked with Banking domain clients like JP Morgan Banking group (4 years’ experience)
• Excellent QA experience in all phases of Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC).
• Good Experience and Knowledge in different project management models like waterfall and Agile Scrum.
• Expertise in Functional, Integration, Regression, SIT, Black Box and User Acceptance Testing (UAT).
• Extensive experience in creating Testing milestones like Test Plans, Test Scenarios, Test Strategies, Test Cases, Test Reports and RTMs.
• Played different roles – as Scrum Master, QA Lead, Senior Tester, SME, BA etc.
• Worked on – Requirement analysis, Test Condition preparation, Test script Creation in Manual & BPT format, Test Execution, Defect life cycle workflow, Performance testing etc.
• Business Analyst experience in working closely with product partners, defining requirements, creating design documents and interface diagrams.
• Dedicated, conscientious individual with strong sense of responsibility, work flexibility and adaptation to changing environments professionally and personally.
DRB EXP RESUME manual and selenium master copy corrected 2Dikhit Behera
Dikhit Ranjan Behera has over 2 years of experience in information technology, including 1 year of experience with automation testing using Selenium. He has skills in manual testing, automation testing with Selenium and TestNG, defect tracking with tools like HPQC and Jira, and programming languages like Java. He currently works as an Associate Software Engineer at Mphasis Limited, where he has been involved in testing projects including an asset management system and a healthcare application.
Altaf Lakhani is an experienced software tester with over 3 years of experience testing web and client-server applications in various industries. He has extensive experience with manual and automation testing using Selenium WebDriver, SQL queries, and tools like Jira. His most recent role was as a QA Automation Tester at A-Z Wholesale in Dallas, where he automated test cases using Selenium and participated in Agile ceremonies. He has experience developing test plans, executing test cases, and documenting defects.
The document provides a professional synopsis for an individual with 3 years of experience in software testing. It summarizes their experience in various testing types such as functional, regression, scenarios, and database testing. It also lists the tools used like Selenium, Bugzilla, and TestNG framework. Finally, it outlines 3 projects the individual worked on, including their roles of preparing and executing test cases, identifying defects, and automation testing using Selenium.
This resume summarizes Chenchaiah Challa's qualifications and experience as a software tester. He has a B.Tech in Electrical and Electronic Engineering from Jawaharlal Nehru Technological University. He underwent 4 months of testing training at LiveTech, Hyderabad where he learned to understand requirements, design test cases, and perform functionality, compatibility, and regression testing. He has experience using testing tools like QTP and defect tracking tools like Bugzilla and TestLink. His most recent project involved testing an insurance application at LiveTech where he created test scripts and cases, performed black box and regression testing, and reported defects.
This document summarizes the skills and experience of Jenifer Breeze. She has over 3 years of experience in software development and testing. She has expertise in web application development using Java technologies and databases like Oracle and MySQL. She is proficient in development, manual testing, automation testing, ETL, and database testing. She has worked on projects for clients in various domains and roles including senior tester, tester, and software developer. Her skills include preparing documentation, developing test cases, unit testing, and ensuring quality.
- Vishwanath G Teli is seeking a position that allows him to utilize his skills in manual testing, Java, SQL and continuous self-development.
- He has over 2 years of experience in software testing and has worked on projects for Hindustan Unilever Ltd. testing tools like NetSuite and GChaRM.
- His responsibilities have included requirement collection, test case design, defect logging, regression testing and creating test reports.
Yogeshwaran has over 5 years of experience in manual and automation software testing using Selenium with Java. He currently works as a QA Analyst at Oracle India and has previous experience working as a Software Engineer at CGI. Some of his key skills include Selenium, JUnit, MySQL, ALM, JIRA, and Oracle Test Manager. He has experience testing projects in domains such as project management, energy/utilities, and machine-to-machine. Notable past projects include testing Primavera P6 Professional Project Management software and the UK's DCC smart meter system. He holds a B.E. in computer science and is ITIL certified.
This document provides an overview of software testing concepts related to manual testing. It discusses key topics like software quality, software quality assurance, software quality control, requirements gathering, design, programming, integration testing, system testing, and more. The document is intended to educate readers on software testing processes and techniques.
The document discusses key concepts in software testing including software quality, software quality assurance (SQA), software quality control (SQC), and the V-Model. It describes the software development lifecycle including requirements gathering, design, coding, testing, and maintenance. It provides details on different types of testing like unit testing, integration testing, system testing, and reviews/inspections conducted at various stages. Key testing techniques mentioned are black box testing, white box testing, basis path testing, control structure testing, and mutation testing. The V-Model mapping development stages to corresponding testing stages is also explained.
The document discusses various stages in the software development life cycle (SDLC) including reviews, testing, and maintenance. It describes reviews that take place during analysis and design to verify requirements and design documents. Unit testing involves testing individual programs using techniques like basic path coverage. Integration testing combines programs to test interfaces. System testing is conducted by a separate team and includes usability, functional, and non-functional testing. User acceptance testing collects customer feedback. Maintenance involves addressing change requests and improving testing processes. The "V" model is presented as an extension of the traditional waterfall SDLC model.
This document provides an overview of software testing concepts for beginner software testers. It discusses key concepts like software quality assurance, software quality control, requirements gathering, reviews, design, programming, testing techniques like black box testing and white box testing, integration testing, system testing, user acceptance testing, and release and maintenance. Testing responsibilities are mapped to different phases and techniques that testing teams can use to verify and validate the software.
This document provides an overview of software testing concepts for beginner software testers. It discusses key concepts like software quality assurance, software quality control, requirements gathering, reviews, design, programming, testing techniques like black box testing and white box testing, integration testing, system testing, user acceptance testing, and release and maintenance. Testing responsibilities are mapped to different phases and techniques that testing teams can use at each phase like walkthroughs, inspections, and regression testing. The document aims to give beginners a comprehensive understanding of the software testing process.
The document discusses the Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC). It describes the various phases of SDLC like requirements gathering, analysis, design, coding, testing, and deployment. It then explains the stages of STLC in more detail - requirements analysis, test planning, test case development, environment setup, test execution, and test closure. Finally, it provides definitions related to the bug life cycle and its flow chart.
The document discusses various aspects of software development including:
1. Software quality focuses on meeting customer requirements and expectations in terms of functionality, performance, cost and time to market.
2. Common software development process models include waterfall, prototype, spiral and agile models which are suited for different types of requirements.
3. Testing is a critical part of the development process and includes unit, integration, system and user acceptance testing. System testing involves testing functionality, usability, compatibility and other quality attributes.
This document provides an overview of software testing concepts including the software development life cycle, different testing methodologies, levels of testing, environments, process models, types of testing, and the software testing life cycle. It defines key terms and describes the roles and processes involved in each phase of development and testing. The document is intended as a manual on software testing engineering principles and practices.
The document discusses software testing and the software development life cycle (SDLC). It provides an agenda that covers topics like types of testing, test case design, bug tracking, and SDLC models. The SDLC models discussed include waterfall, V-model, spiral model, and agile development models. The document describes the phases of the waterfall model SDLC such as requirements gathering, analysis, design, coding, testing, and deployment/maintenance.
The document discusses the software development life cycle (SDLC) process. It includes 6 main steps: 1) requirement gathering, 2) software analysis, 3) software design, 4) coding, 5) testing, and 6) implementation. For each step, the document provides details on the objectives and activities involved. It also lists advantages of following the SDLC process such as increased quality, improved tracking, and decreased risks. Finally, it provides a coding example for a basic calculator application to illustrate one step of the process.
The document discusses software testing fundamentals and principles. It defines software testing as evaluating a product to determine if it contains any defects and satisfies requirements. Testing is important to prevent errors and ensure quality, security, efficiency and flexibility. The key goals of testing are to find defects, verify that specifications are properly implemented, and ensure customer expectations are met.
The document discusses software development lifecycles and strategies. It describes:
1) Common lifecycle activities like planning, development, testing and maintenance. Different models can be used depending on the product.
2) Solution strategies are developed to determine the nature of possible solutions and provide a framework for design and implementation. The best strategies are developed by trained groups using techniques like brainstorming.
3) The phased lifecycle model involves a series of defined activities with inputs, processes, and outputs at each phase. Resources are required to complete each defined phase.
The document discusses various aspects of planning and managing the software development process, including:
1) Developing a solution strategy and selecting a software life cycle model to provide a framework for the project.
2) Common software life cycle activities like planning, development, testing, and maintenance.
3) Using milestones, documents, and reviews to improve project visibility and management.
4) Organizing development tasks and teams using different structures like project, functional, and matrix formats.
1. The document describes various testing documents created at different levels of a project testing process. Test policy, strategy, and methodology documents are created at higher levels, while test plans, cases, procedures, scripts, and reports are created at the project level.
2. It provides details on different testing documents - test policy defines testing objectives, test strategy defines the testing approach, and test methodology provides the testing approach for a specific project. It also describes how test plans are created, test cases are designed based on requirements, and the different levels of test execution.
3. The key testing documents created are test policy, strategy, methodology, plan, cases, procedures, scripts, and reports. Test cases are designed based
The document discusses the waterfall model of software development. It describes the six phases of the waterfall model as preliminary investigation and feasibility analysis, requirement analysis, system design, coding, integration and testing, and implementation and maintenance. For each phase, specific activities are outlined such as collecting requirements, designing system architecture and algorithms, programming code, integrating and testing units of code, and deploying the software for use. In conclusion, the waterfall model is described as a well-organized approach that leads to reliable software development when phases are completed sequentially.
MindScripts Technologies is the authorized Softwrae Testing Training institutes in Pune, providing a complete softwrae testing certification course with ISTQB certification. It provides a IBM Certified courses.
DevOps aims to shorten the development lifecycle by integrating development and testing. This presentation discusses implementing continuous integration testing for System z applications using Rational Developer for zSystems, Rational Development and Test, Rational Team Concert, and Optim Test Data Management. It demonstrates how these tools allow developers to check code in and out of source control, build and test code on sandbox environments, run automated tests, and report results. This enables faster feedback and higher quality code.
This document discusses the different types of statements used in QuickTest Professional (QTP) test scripts, including declarations, comments, utility statements, object calls, flow control statements, function/action calls, checkpoints, output value statements, synchronization points, and VBScript statements. Declarations are used to define variables and constants. Comments explain parts of the test script. Utility statements launch applications and control program flow. Object calls interact with application objects. Flow control statements include if/else, select case, loops, and more. Functions and actions encapsulate reusable code. Checkpoints and output values verify test results. Synchronization waits ensure objects are ready. VBScript provides additional programming constructs.
HTML Interview Questions provides answers to common HTML questions. Some key points:
- There is no reliable way to indent paragraphs or large blocks of text in HTML due to inconsistent browser support. Workarounds like non-breaking spaces can be used but may not work across all browsers.
- To center a table, use <CENTER> tags around the entire table. Individual cell contents can be aligned left using <P ALIGN=left> for browser compatibility.
- Character entities are allowed in ALT text but other markup is not permitted.
- To redirect users, configure the server to send a redirection instruction. Alternatively provide a notice on the page directing users to the new URL.
- There is
QuickTest 11.00 offers new features such as managing test data through Quality Center test configurations, testing GUI and non-GUI application layers in a single test, and a new Run Results Viewer. It also provides improved support for technologies like Web 2.0, Silverlight, and WPF applications as well as enhanced documentation.
This document outlines a 40-hour training course on QuickTest Professional 10.00 with a scripting orientation. The course covers topics such as the QTP test process, key elements, recording and running tests, object repositories, descriptive programming, checkpoints and output values, parameterization, synchronization, actions, debugging tests, Quality Center integration, VBScript, file system operations, the Excel object model, database modeling, regular expressions, error handling, GUI scripting, web scripting, and automation frameworks. The course is divided into 29 sessions spanning these topics.
This document provides guidelines for creating a folder structure for testing an e-commerce portal called IBEEeCom. It outlines creating a main project folder with subfolders for modules like Admin and User. It also describes subfolders within the Admin folder for requirements, reports, change requests, test cases, defects and automation. The automation subfolder further divides test automation documents between QuickTest Professional and LoadRunner. Testers are instructed to first create the project folder structure locally and then check it into version control.
This document outlines a 50-hour training course on QTP (QuickTest Professional) with a scripting orientation. The course is divided into 4 modules that cover QTP fundamentals, VB scripting, QTP scripting, and automation frameworks. The prerequisites include software testing principles, QTP basics, programming fundamentals, and database fundamentals. The trainer, Mr. G C Reddy, has over 10 years of IT experience including 7 years of teaching and performing software testing.
The document provides an overview of QuickTest Professional (QTP), a test automation tool. It discusses QTP's key features, the testing process using QTP, and an introduction to using VBScript with QTP for test automation. The document outlines QTP's object repository, test creation features like recording and checkpoints, debugging tests, integrating with Quality Center, and more. It also provides an introduction to using VBScript for programming tests within QTP.
The document provides details about QTP commands available through menus and toolbars to create, open, save, edit, run and manage tests. Key commands allow creating tests and components, opening existing tests, saving tests, editing steps, inserting checkpoints and scripts, recording and running tests, and managing test runs. QTP commands are accessible through menu options, toolbar buttons, and shortcut keys for important operations.
The document discusses QuickTest Professional (QTP) object repositories, which store object information to identify objects during test execution. There are four types of objects - runtime objects from the application under test, test objects that reference runtime objects, utility objects used for testing, and user-defined objects. The object repository acts as an interface between test scripts and the application. Users can perform operations like adding, renaming, deleting objects in both local and shared repositories.
The document outlines an advanced 50-hour QuickTest Professional (QTP) training program. The program covers topics such as test automation basics, the QTP IDE, the testing process, VBScript, working with files, automating Windows and web applications, error handling, and designing automation frameworks. It provides overviews of the chapters and highlights hands-on examples that will be covered. Background knowledge in software testing, programming, databases, and QTP basics is recommended for participants. The instructor, G.C. Reddy, has 7+ years of experience in software testing and has trained professionals on QTP and testing.
The document provides an introduction to advanced QTP concepts using VBScript orientation. It discusses VBScript variables including data types, operators, input/output operations, constants, conditional statements, procedures, built-in functions, and syntax rules. The document also covers topics like errors, file system operations, test requirements, solutions, and QTP add-ins. It recommends visiting an external website for more QTP information, scripts, and manual testing documents.
The document provides an overview of QuickTest Professional (QTP) and its key features and functionality. It discusses QTP's basic features, the elements that make up the QTP tool window like the test pane, active screen, and data table. It also summarizes the QTP testing process which involves planning, generating tests through recording or programming, enhancing tests with checkpoints and parameters, debugging, running tests, and reporting results.
The document provides examples of scripts for performing various operations using VBScript including file system operations, accessing a database to retrieve test data, interacting with browsers and web pages, and manipulating Excel files. The scripts demonstrate how to create and check for files, retrieve data from an Access database to use for data-driven testing, count open browsers and links on a web page, create an Excel file and enter data, and read test data from an external Excel sheet.
The document discusses various methods for working with files, folders, drives, flat files, word documents, and excel sheets using Visual Basic Script. Some key methods include creating, deleting, copying, and checking folders; getting drive information; reading from and writing to flat files; creating, saving and comparing word documents and excel files. The document provides code examples for performing each of these file operations.
The document contains 55 questions related to QuickTest Professional (QTP) automation testing. The questions cover topics like the QTP testing process, object identification, test case automation, parameterization, checkpoints, object repositories, dynamic object handling, descriptive programming, and more. The document was provided by a QTP trainer based in Hyderabad, India who offers training on QTP and can answer questions related to the tool.
The document discusses the key elements of QuickTest Professional (QTP), including the test pane, active screen, data table, debug viewer, and other windows. It describes object repositories, types of objects in QTP, and operations on repositories like adding, renaming and deleting objects. The QTP testing process is outlined, covering planning, generating tests, enhancing tests with checkpoints, parameters, programmatic statements, and debugging. Advanced QTP features and VBScript for QTP are also summarized, with sections on variables, data types, operators, conditional statements, loops, procedures, functions, objects and errors in VBScript.
The document provides an overview of VBScript including:
1) It describes VBScript as a lightweight scripting language that is interpreted by the Windows Script Host.
2) It lists common hosting environments for VBScript like web pages and Windows Script Host.
3) It discusses VBScript syntax rules and elements like variables, data types, operators, and input/output functions.
4) It provides examples of how to write VBScript code for comments, variables, constants, and other language elements.
The document defines various technical terms related to web development and computing. It provides definitions for terms like ActiveMovie, ActiveX, Address, Anchor, Anonymous FTP, ANSI, and ADO among many others. Each term is defined in 1-2 sentences to concisely explain its meaning or purpose.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
How RPA Help in the Transportation and Logistics Industry.pptxSynapseIndia
Revolutionize your transportation processes with our cutting-edge RPA software. Automate repetitive tasks, reduce costs, and enhance efficiency in the logistics sector with our advanced solutions.
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
BT & Neo4j: Knowledge Graphs for Critical Enterprise Systems.pptx.pdfNeo4j
Presented at Gartner Data & Analytics, London Maty 2024. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Join this session to hear their story, the lessons they learned along the way and how their future innovation plans include the exploration of uses of EKG + Generative AI.
7 Most Powerful Solar Storms in the History of Earth.pdfEnterprise Wired
Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).
Support en anglais diffusé lors de l'événement 100% IA organisé dans les locaux parisiens d'Iguane Solutions, le mardi 2 juillet 2024 :
- Présentation de notre plateforme IA plug and play : ses fonctionnalités avancées, telles que son interface utilisateur intuitive, son copilot puissant et des outils de monitoring performants.
- REX client : Cyril Janssens, CTO d’ easybourse, partage son expérience d’utilisation de notre plateforme IA plug & play.
How Social Media Hackers Help You to See Your Wife's Message.pdfHackersList
In the modern digital era, social media platforms have become integral to our daily lives. These platforms, including Facebook, Instagram, WhatsApp, and Snapchat, offer countless ways to connect, share, and communicate.
Mitigating the Impact of State Management in Cloud Stream Processing SystemsScyllaDB
Stream processing is a crucial component of modern data infrastructure, but constructing an efficient and scalable stream processing system can be challenging. Decoupling compute and storage architecture has emerged as an effective solution to these challenges, but it can introduce high latency issues, especially when dealing with complex continuous queries that necessitate managing extra-large internal states.
In this talk, we focus on addressing the high latency issues associated with S3 storage in stream processing systems that employ a decoupled compute and storage architecture. We delve into the root causes of latency in this context and explore various techniques to minimize the impact of S3 latency on stream processing performance. Our proposed approach is to implement a tiered storage mechanism that leverages a blend of high-performance and low-cost storage tiers to reduce data movement between the compute and storage layers while maintaining efficient processing.
Throughout the talk, we will present experimental results that demonstrate the effectiveness of our approach in mitigating the impact of S3 latency on stream processing. By the end of the talk, attendees will have gained insights into how to optimize their stream processing systems for reduced latency and improved cost-efficiency.
YOUR RELIABLE WEB DESIGN & DEVELOPMENT TEAM — FOR LASTING SUCCESS
WPRiders is a web development company specialized in WordPress and WooCommerce websites and plugins for customers around the world. The company is headquartered in Bucharest, Romania, but our team members are located all over the world. Our customers are primarily from the US and Western Europe, but we have clients from Australia, Canada and other areas as well.
Some facts about WPRiders and why we are one of the best firms around:
More than 700 five-star reviews! You can check them here.
1500 WordPress projects delivered.
We respond 80% faster than other firms! Data provided by Freshdesk.
We’ve been in business since 2015.
We are located in 7 countries and have 22 team members.
With so many projects delivered, our team knows what works and what doesn’t when it comes to WordPress and WooCommerce.
Our team members are:
- highly experienced developers (employees & contractors with 5 -10+ years of experience),
- great designers with an eye for UX/UI with 10+ years of experience
- project managers with development background who speak both tech and non-tech
- QA specialists
- Conversion Rate Optimisation - CRO experts
They are all working together to provide you with the best possible service. We are passionate about WordPress, and we love creating custom solutions that help our clients achieve their goals.
At WPRiders, we are committed to building long-term relationships with our clients. We believe in accountability, in doing the right thing, as well as in transparency and open communication. You can read more about WPRiders on the About us page.
Quantum Communications Q&A with Gemini LLM. These are based on Shannon's Noisy channel Theorem and offers how the classical theory applies to the quantum world.
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
Understanding Insider Security Threats: Types, Examples, Effects, and Mitigat...Bert Blevins
Today’s digitally connected world presents a wide range of security challenges for enterprises. Insider security threats are particularly noteworthy because they have the potential to cause significant harm. Unlike external threats, insider risks originate from within the company, making them more subtle and challenging to identify. This blog aims to provide a comprehensive understanding of insider security threats, including their types, examples, effects, and mitigation techniques.
Understanding Insider Security Threats: Types, Examples, Effects, and Mitigat...
Manual Testing
1. gcrindia@gmail.com
Manual Testing
Software Quality:
Software satisfies quality only when it meets to Customer Requirement / Customer
Satisfaction / Customer Expectations. Meets Customer Requirement refers to proper output
& Customer Expectations refers to extra characteristics, good interface, speed, privacy,
security, easy to operate, good functionality.
Non-technical reasons: Cost of product & Time to market
Software Quality Assurance:
SQA are the Concepts to be followed by company to develop the software. An SQA
team is responsible for Monitoring & Measuring the strength of developing processes.
Software Project:
A set of problems assigned by the client, who can be solved by the software people
through the process of software Engineer called Software project. In short, the problem, the
people, the process called project. Software related problem is solved by software engineers
through software engineer process is software project.
Software Development Life Cycle / Life Cycle Development:
Stages involved in software project development
1) Information gathering; Customer requirement
2) Analysis; Customer requirement v/s Solutions
3) Design; Dividing the project into modules & coupling them
4) Coding; Physical construction of project
5) Testing
6) Maintenance
Information gathering stage:
In this stage, Business Analyst studies the requirement of the client /customer and
they prepare Business Requirement Specification (BRS) documents.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 1
2. gcrindia@gmail.com
Analysis:
In this stage, Sr. Analyst prepares Software Requirement Specification (S/w RS)
document with respect to corresponding BRS document. This document consists of two
sub-documents System Requirement Specification (SRS) & Functional Requirement
Specification (FRS). SRS contain details about software & hardware requirement. FRS
contains details about the functionality to be used in project.
Designing:
In designing phase, Designers creates two documents High Level Document (HLD)
& Low Level Document (LLD). HLD consists of main modules of the project from root to
leaf and multiple LLD’s. LLD consists of sub-modules of main module along with Data
flow diagrams, ER-Diagrams, etc., are prepared by technical support people or designers
called Internal designers.
• Black box tester should have knowledge of customer requirement
• Black box testing tests BRS & SRS
• Testing external interfacing is Black box testing
• Testing internal interfacing is White box testing
• White box testing is done w.r.t design documents
Testing:
V MODEL TESTING
Development Testing
Assesment development plan
Prepare Test plan
Information Requirement phase testing
Design phase testing
Programme phase testing
Design & Coding
Functional system testing
User acceptance testing
Install Build Test documentation
Port testing
Maintenance Test Software changes
Test efficiency
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 2
3. gcrindia@gmail.com
* Test plan is developed based on Development plan
Formula for test efficiency: DRE = A / A + B
DRE = Defect Removal Efficiency
A -> Bugs found at the testing side
B -> Bugs found at the client side
DRE= 0.8 – 0.9 good
0.7 – 0.8 requires improvement
< 0.7 poor
Refinement Form of V-Model
BRS / URS/ CRS User Acceptance Test
S/w RS Black box Testing
HLD’s Integration Testing
LLD’s Unit Testing
Coding
From the above refinement form of V-Model, small & medium scale organizations
are maintaining separate testing team for Functional & System testing stage.
1) Reviews during Analysis
In general, Software development process starts with Information Gathering &
Analysis. In this stage Business Analyst category people are preparing BRS & S/w RS
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 3
4. gcrindia@gmail.com
documents and after completion documents preparation, they conduct reviews on the
documents for completeness & correctness. This review focuses on below factors:
1) Are they complete
2) Are they met with right requirements of client / customer
3) Are they achievable w.r.t technology
4) Are they reasonable w.r.t time & cost
5) Are they testable
2) Reviews during Design
After completion of Analysis phase & their reviews, our Project-level designers will
start logical design of application in terms of External & Internal design (HLD’s & LLD’s).
In this stage, they conduct reviews for completeness & correctness of designed documents.
This review focuses on below factors:
1) Are they understandable
2) Are they met with right requirements of client / customer
3) Are they complete
4) Are they follow able
5) Does they handle errors
3) During Unit Testing
After completeness of Design & their reviews, software programmers will starts
coding the logical design to physical construction of software. During these coding stage
programmers is conducting Unit Testing through a set of White box testing techniques, Unit
Testing also known as Module / Component / Program / Micro testing
White box Testing:
There are three possible White box testing techniques
1) Execution Testing
Basic path coverage – Execution of all possible blocks in a program
Loops coverage – Termination of loop statements
Programmer technique coverage – less no of memory cycles & CPU cycles
2) Operation Testing – Running the application on Customer expected platforms
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 4
5. gcrindia@gmail.com
3) Mutation Testing
Mutation means that a change program. White box testers are performing the change
in the program to estimate test coverage on that program. Mutation testing can decide
whether the test coverage is correct or wrong
4) Integration Testing
After completion of dependent modules of development & testing, Programmers
combine them to form a System. In this Integration, they are conducting Integration testing
on the compiled modules w.r.t HLD.
There are three approaches to conduct Integration testing
a) Top-Down Approach
Mai
Stub
Sub 1 Sub 2
Top-Down Approach
In this approach, testing is conducted on Main module without conducting testing to
some of sub-modules. From the above diagram, a Stub is a temporary program instead of
under constructive sub-module, it is known as called program.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 5
6. gcrindia@gmail.com
b) Bottom-Up Approach
Main
Driver
Sub 1
Sub 2
Bottom-Up Approach
In this approach, testing is conducted on sub-modules without conducting testing on
main modules. From the above diagram, a Driver is a temporary program instead of main
module, it is known as calling program.
c) Sandwich or Hybrid Approach
Main
Driver
Sub 1
Stub
Sub 2
Sub 3
Sandwich / Hybrid Approach
In this approach, testing is conducted taking both Top-Down & Bottom
Approaches.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 6
7. gcrindia@gmail.com
* Build: A finally integrated all modules set *.exe form file is called build.
4) Functional & System testing (* imp)
After completion of final integration of modules as a system, Testing Engineers are
planning to conduct Functional & System testing through Black box testing techniques,
these techniques classified into four categories.
1) Usability Testing
2) Functional Testing
3) Performance Testing
4) Security Testing
From Above 1 & 2 are Core level and 3 & 4 are Advance level
During Usability testing, Testing team validates User-Friendliness of screens.
During Functional testing, TT validates the correctness of customer requirements
During Performance testing, TT estimates speed of processing
During Security testing, Testing team validates privacy to User operations
1) Usability Testing
In general, TT starts with test execution with Usability testing. During test, Testing
team validates User-Friendliness of screens of build. During Usability testing, TT applies two
types of sub-test:
a) User Interface Test
Easy of use (Understandable screens)
Look & Feel (Attractiveness & Pleasantness)
Speed in Interface (Less no of event to complete a test, easy short navigation)
b) Manual Support Test
Context sensitiveness of user manuals
Manual support test are conducted at the end of all testing & before release
2) Functional Testing
The major part of Black box testing is Functional testing, during this test, Testing
team1 concentrates on “meet customer requirements”. This Functional Testing is classified
into below sub-test.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 7
8. gcrindia@gmail.com
a) Functional / Requirement Testing
During this test, Test Engineers validates correctness of every functionality in terms
of below coverage’s.
Behavioral coverage (changes in object properties)
Input domain coverage (size & type of every input & output object)
Error handling coverage (preventing negative navigations)
Calculations coverage (correctness of output)
Back-end coverage (impact of Front-end operation on back-end tables contents)
Service levels coverage (order of functionalities)
b) Input Domain Testing
It is a part of Functionality testing; Test Engineers are maintaining special structures
to define size & type of input object
c) Recovery Testing
It is also known as Reliability testing. During this test, Testing team validates
whether the application is changing from abnormal state to normal state or not.
d) Compatibility Testing
It is also known as Portability testing. During this test, Testing team validates
whether application build run on customer expected platforms or not. During this test,
Testing Engineers are finding Backward compatibility at maximum.
Forward compatibility -> application is ready to run but Operating system is not
supporting.
Backward compatibility -> Operating system is supporting but the application has
some internal coding problems to run on Operating system
e) Configuration Testing
It is also known as Hardware compatibility testing. During this test, Testing team
validates whether application build supports different technology Hardware devices or not.
f) Inter-Systems Testing
During this test, Testing team validates whether application build co-existence with
other existing software’s or not and also test whether any Dead lock situation occurs or not.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 8
9. gcrindia@gmail.com
g) Installation Testing
During this test, Testing team validates whether application build along with
supported software’s into customers site like configured systems. During this test, Testing
team observes below factors.
Setup program execution to start installation
Easy Interface
Amount of disk occupied after installation
h) Parallel / Comparative Testing
During this test, Testing team compares application build with competitive products
in market.
i) Sanitation / Garbage Testing
During this test, Testing team tries to find extra features in application build w.r.t
customer requirements.
* Defects
During this test, Testing team reports defects to developers in terms of below
categories
1. Mismatches between expected & actual
2. Missing functionality
3. Extra functionality w.r.t customer requirement
* Manual v/s Automation
A Tester conducts any test on application build without using any testing tool is
called Manual testing, if any testing tool is used then it is called Automation testing
In common testing process, Testing Engineers are using test Automation w.r.t test
impact & criticality. Impact -> test repetition & Criticality -> complex to apply test
manually. Due to these two reasons testing people are using test Automation.
j) Re-testing
The re-execution of a test with multiple test data to validate a function, e.g. To
validate multiplication, Test Engineers use different combinations of input in terms of min,
max, -ve, +ve, zero, int, float, etc.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 9
10. gcrindia@gmail.com
k) Regression Testing
The re-execution of test on modified build to ensure bug fixing work & occurrence
of any side effects, Test Engineers conducts this test using Automation
l) Error, Defect & Bug
A mistake in code is Error, due to errors in coding, Test Engineers are getting
mismatches in application build are defects, if the defects are accepted by developers to be
solves then it is Bug.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 10
11. gcrindia@gmail.com
Testing Documents
Test Policy
Test Strategy
Test Methodology
Test Plan
Test Cases
Test Procedure
Test Script
Defect Report
Final Test Summary Report
Above Figure, shows the various levels of documents prepared at project testing.
Test Policy is documented by Quality Control. Test Strategy & Test Methodology are
documented by Quality Analyst or Project Manager. Test Plan, Test Cases, Test Procedure,
Test Script & Defect Report are documented by Quality Assurance Engineers or Test
Engineers.
Test Policy & Test Strategy are Company Level Documents. Test Methodology, Test
Plan, Test Cases, Test Procedure, Test Script, Defect Report & Final Test Summary Report
are Project Level Documents.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 11
12. gcrindia@gmail.com
1) TEST POLICY:
This document developed by Quality Control people (Management). In this
document Quality Control defines “Testing Objective”.
Test Policy Document
Address of the Company
Test Definition : Verification & Validation
Testing Process : Proper planning before starts testing
Testing Standards : One defect per 250 lines of code or 10 FP (Functional points)
Testing Measurements : QAM, TTM, PCM
*******
(C.E.O)
QAM: Quality Assurance Measurements, how much quality is expected
TTM: Testing Team Measurements, how much testing is over & is yet to complete
PCM: Process Capability Measurements, depends on old project to the upcoming projects.
2) TEST STRATEGY:
This is a Company level document & developed by Quality Analyst or Project
Manager Category people, it defines “Testing Approach”.
Components:
a) Scope & Objective: Definition & purpose of testing in organization
b) Business Issue: Budget control for testing
c) Test Approach: Mapping between development stages & Testing Issue.
d) Test Deliverables: Required testing documents to be prepared
e) Roles & Responsibilities: Names of the job in testing team & their responsibilities
f) Communication & Status reporting: Required negotiation between testing team &
developing team during test execution
g) Automation & Testing Tools: Purpose of automation & possibilities to go to test
automation
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 12
13. gcrindia@gmail.com
h) Testing Measurements & Metrics: QAM, TTM, PCM
i) Risks & Mitigation: Possible problems will come in testing & solutions to overcome
j) Change & Configuration Management: To handle change request during testing
k) Training Plan: Required training sessions to testing team before start testing process
Testing Issues:
1. Authorization: Whether user is valid or not to connect to application
2. Access Control: Whether a valid user have permission to use specific service
3. Audit Trail: Maintains metadata about user operation in our application
4. Continuity of Processing: Inter-process communication
5. Correctness: Meet customer requirement in terms of functionality
6. Coupling: Co-existence with other existence software to share resources
7. Ease of Use: User Friendliness of the screens
8. Ease of Operator: Installation, Un-installations, Dumping, Uploading,
Downloading, etc.,
9. File Integrity: Creation of backup
10. Reliability: Recover from abnormal state
11. Performance: Speed of processing
12. Portable: Run on different platforms
13. Service levels: Order of functionalities
14. Maintainable: Whether our application build is long term serviceable to our
customer
15. Methodology: Whether our tester are following standards or not during testing
3) TEST METHODOLOGY:
It is project level document. Methodology provides required testing approach to be
followed for current project. In this level Quality Analyst select possible approach
for corresponding project testing.
Test Test Test Test Test
Initiation Planning Designing Execution Closure
Test
Reporting
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 13
14. gcrindia@gmail.com
Pet Process:
Process involves experts, tools & techniques. It is a refinement form of V-Model. It
defines mapping between development & Testing stages. From this model, Organizations
are maintaining separate team for Functional & System testing & remaining stages of testing
done by development people. This model is developed in HCL & recognized by QA Forum
of INDIA.
TESTING PROCESS
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 14
15. gcrindia@gmail.com
Information Gathering (Business Requirement Specifications)
Analysis (Software Requirement Specification)
Design Test Initiation
Coding Test Planning & Training
Unit & Integration Test Design
Test Cases Selection & Closure
Level – 0
Sanity / Smoke / Tester Acceptance Test / Build Verification Test
Test Automation
Create Test Suits / Test Batches / Test Sets
Defect fixing Level – 1
& Resolving Select a batch & starts execution
Developers If Mismatch, then suspend the batch
Otherwise
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 15
16. gcrindia@gmail.com
Test Closure
Level – 3
Final Regression / Releasing Testing / Pre-Acceptance / Post-Mortem testing
User Acceptance Testing
Sign Off
4) TEST PLANNING:
After finalization of possible test for current project, Test Lead category people
concentration on test plan document preparation to define work allocation in terms of What,
Who, When & How to test. To prepare test plan document, test plan order follows below
approach;
Development
document Team Formation
Identify Tactical Risks System Test Plan
Prepare Test Plan
Test Responsible
Review Test Plan
Matrix
1] Team Formation:
In general, Test planning process starts with testing team formation. To define a
testing team, test plan author depends on below factors;
1. Availability of testers
2. Test duration
3. Availability of test environment resource
2] Identify Tactical Risk:
After Testing team formation Plan author analysis possible & mitigation (ad hoc
testing)
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 16
17. gcrindia@gmail.com
# Risk 1: Lack of knowledge of Test Engineer on that domain
# Soln 1: Extra training to Test Engineers
# Risk 2: Lack of Resource
# Risk 3: Lack of budget {less no of time}
# Soln 3: Increase Team size
# Risk 4: Lack of Test data
# Soln 4: Conduct test on past experience basis i.e., ad hoc testing or contact client for data
# Risk 5: Lack of developer process rigor
# Soln 5: Report to Test Lead for further communication between test & development PM
# Risk 6: Delay of modified build delivery
# Soln 6: Extra hours of work is needed
# Risk 7: Lack of communication in between Test Engineer - > Test team and
Test team - > Development team
3] PREPARE TEST PLAN:
After completion of testing team formation & Risk analysis, Test plan author
concentrate on Test Plan Document in IEEE format.
01) Test Plan ID: Unique No or Name e.g. STP-ATM
02) Introduction: About Project description
03) Test Items: Modules / Functions / Services / Features / etc.
04) Features to be tested: Responsible Modules for Test design (preparing test cases for
added modules)
05) Features not to be tested: Which feature is not to be tested and Why? (Due to test
cases available for the old modules, so for these modules no
need to be tested / no test case
Above (3), (4) & (5) decides which module to be tested – > What to test?
06) Approach: List of selected testing techniques to be applied on above specified
modules in reference to the TRM(Test Responsible Matrix).
07) Feature pass or fail criteria: When a feature is pass or fail description
(Environment is good) (After testing conclusion)
08) Suspension criteria: Possible abnormal situations rose during above features testing
(Environment is not good) (During testing conclusion)
09) Test Environment: Required software & Hardware to be tested on above features
10) Test Deliverables: Required testing document to be prepared (during testing, the type
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 17
18. gcrindia@gmail.com
of documents are prepared by tester)
11) Testing Task: Necessary tasks to do before start every feature testing
Above (6) to (11) specifies -> How to test?
12) Staff & Training: Names of selected Test Engineers & training requirements to them
13) Responsibilities: Work allocation to every member in the team (dependable modules
are given to single Test Engineer)
14) Schedule: Dates & Times of testing modules
Above (4) specifies -> When to test?
15) List & Mitigation: Possible testing level risks & solution to overcome them
16) Approvals: Signatures of Test plan authors & Project Manager / Quality Analyst
4) Review Test Plan:
After completion of plan document preparation, Test plan author conducts a review
of completion & correctness. In this review, Plan author follows below coverage analysis
BRS based coverage (What to test? Review)
Risks based coverage (When & Who to test? Review)
TRM based coverage (How to test? Review)
5) TEST DESIGNING:
After completion of Test Planning & required training to testing team,
corresponding testing team members will start preparing the list of test cases for their
responsible modules. There are three types of test cases design methods to cover core level
testing (Usability & Functionality testing).
a) Business Logic based test case design (S/w RS)
b) Input Domain based test case design (E-R diagrams / Data Models)
c) User Interface based test case design (MS-Windows rules)
a) Business Logic based Test Case design (S/w RS)
In general, Test Engineers are preparing a set of Test Cases depends on Use Cases in
(S/w RS). Every Use Case describes a functionality in terms of inputs, process & output,
depends on this Use Cases Test Engineers are preparing Test Cases to validate the
functionality
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 18
19. gcrindia@gmail.com
BRS
Test
Use Cases & Cases
Functional
Cases
HLD’s
LLD’s
Coding
*.exe
From the above model, Test Engineers are preparing Test Cases depends on
corresponding Use Cases & every test case defines a test condition to be applied.
To prepare test cases, Test Engineers studies Use Cases in below approach:
Steps:
1) Collect Use Cases of our responsible module
2) Select a Use Case & their dependencies from the list
2.1) Identify entry condition (Base state)
2.2) Identify input required (Test data)
2.3) Identify exit condition (End state)
2.4) Identify output & outcome (Expected)
2.5) Identify normal flow (Navigation)
2.6) Identify alternative flows & exceptions
3) Write Test Cases depends on above information
4) Review Test Cases for the completeness & correctness
5) Goto step (2) until completion of all Use Cases completion
Use Case I:
A login process allows user id & password to validate users. During these validations,
login process allows user id in alpha-numeric from 4 to 16 characters long & password in
alphabets in lowercase from 4 to 8 characters long.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 19
20. gcrindia@gmail.com
Case study:
Test Case 1) Successful entry of user id
BVA (Size)
min -> 4 chars => pass
min-1 -> 3 chars => fail
min+1 -> 5 chars => pass
max-1 -> 15 chars => pass
max+1 -> 17 chars => fail
max -> 16 chars => pass
ECP
Valid Invalid
a-z special chars
A-Z blank
0-9
Test Case Format:
During Test design Test Engineers are writing list of Test Cases in IEEE format.
01) Test Case ID: Unique no or name
02) Test Case Name: Name of test condition to be tested
03) Feature to be tested: Module / Function / Feature
04) Test suit ID: Batch ID, in which this case is member
05) Priority: Importance of Test Case {Low, Med, High}
P0 -> Basic functionality
P1 -> General functionality (I/P domain, Error handling, Compatibility etc,)
P2 -> Cosmetic testing (UIT)
06) Test Environment: Required Software & Hardware to execute
07) Test afford (person / hr): Time to execute this Test Case e.g. 20 minutes
08) Test duration: Date & Time
09) Test Setup: Required testing task to do before starts case execution (pre-requisites)
10) Test Procedure: Step by step procedure to execute Test Case
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 20
21. gcrindia@gmail.com
Test Procedure Format:
1) Step No:
2) Action: -> Test Design
3) Input required:
4) Expected:
5) Actual:
6) Result: -> Test Execution
7) Comments:
11) Test Case passes or fails criteria: When this case is pass or fail
Note: Test Engineers follows list of Test Cases along with step by step procedures only
Example 1:
Prepare Test Procedure for below test cases “Successful file save operation in Notepad “.
Step Action Input Expected
No Required
1 Open Notepad Empty Editor
2 Fill with text Save Icon enabled
3 Click Save Icon or click File Save Dialog box appears with
menu Default file name
Option & select save option
4 Enter File name & Click Save Unique Focus to Notepad & File
File name name
Appears in title bar of
Notepad
Note: For more examples refer to notes
b) Input Domain based Test Case design (E-R diagrams / Data Models)
In general, Test Engineers are preparing maximum Test Cases depends on Use Cases
or functional requirements in S/wRS. These functional specifications provide functional
descriptions with input, output & process, but they are not responsible to provide
information about size & type of input objects. To correct this type of information, Test
Engineers study Data model of responsible modules E-R diagram. During Data model
study, Test Engineer follows below approach: Steps:
1) Collect Data model of responsible modules
2) Study every input attribute in terms of size, type & constraint
3) Identify critical attributes in the test, which is participated in manipulation & retrivals
4) Identify non-critical attributes such as input & output type
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 21
22. gcrindia@gmail.com
A/C No:
Critical
A/C Name:
Balance:
Non-Critical
Address:
5) Prepare BVA & ECP for every input object
ECP BVA(Size / Range)
Input Attribute Valid Invalid Minimum Maximum
Xxxx xxxx xxxx xxxx xxxx
“ “ “ “ “
“ “ “ “ “
“ “ “ “ “
DATA MATRIX
Note: In general, Test Engineers are preparing step by step procedure based Test Cases for
functionality testing. Test Engineers prepare valid / invalid table based Test Cases for input
domain of object testing {Data Matrix }
Note: For examples refer to notes
c) User Interface based test case design (MS-Windows rules)
To conduct Usability Testing, Test Engineers are preparing list of Test Cases
depends on our organization User Interface standards or conventions, Global User Interface
rules & interest of customer site people.
Example: Test Cases
1) Spelling check
2) Graphics check (Screen level Align, Font style, Color, Size & Microsoft six rules)
3) Meaning of error messages
4) Accuracy of data displayed
5) Accuracy of data in the database are result of user inputs, if developer restrict the data in
database level by rounding / truncating then the developer must also restrict the data in
front-end as well
6) Accuracy of data in the database as the result of external factors. Ex. File attachments
7) Meaningful help messages (Manual support testing)
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 22
23. gcrindia@gmail.com
Review Test Cases:
After completion of all possible Test Cases preparation for responsible modules,
Testing team concentrates on review of Test Cases for completeness & correctness. In this
review, Testing team applies coverage analysis.
Test Case Review
1) BR based coverage
2) Use Cases based coverage
3) Data model based coverage
4) User Interface based coverage
5) TRM based coverage
At the end of this review, Test Lead prepare Requirement Traceability Matrix or
Requirement Validation Matrix (RTM / RVM)
Business Requirement Source (Use Cases, Data model) Test Cases
xxxx xxxx xxxx
xxxx
xxxx
xxxx xxxx
xxxx
xxxx xxxx
xxxx
xxxx
xxxx xxxx xxxx
xxxx
xxxx xxxx
xxxx
xxxx
From RTM / RVM model, it defines mapping between customer requirement &
prepared Test Cases to validate the requirement.
6) TEST EXECUTION:
After completion of Test Cases selections & their review, Testing team concentrate
on Build release from development side & Test execution on that build.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 23
24. gcrindia@gmail.com
a) Test Execution Levels or Phases:
See figure in next page for clear understandability of this levels
b) Test Execution Levels v/s Test Cases:
Level – 0 -> P0 Test Cases
Level – 1 -> All P0, P1 & P2 Test Cases as batches
Level – 2 -> Selected P0, P1, & P2 w.r.t modification
Level – 3 -> Selected P0, P1, & P2 w.r.t critical areas in the master build
A) Test Execution Levels or Phases:
Initial Build
Stable Build Level – 0
Sanity / Smoke / ….
Defect Defect Report
Level – 1
Fixing Comprehensive
Modified build Level – 2
Defect
Resolving Regression
Level – 3
Final Regression
c) Build Version Control:
In general, Testing Engineers are receiving build from development in below model
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 24
25. gcrindia@gmail.com
Build
Server
FTP (file transport
Protocol) Testing Environment
Testers
During Test execution Test Engineer are receiving modified build from software. To
distinguish old & new builds, development team maintains unique version in system, which
is understandable to Tester / Testing team. For this version controlling developers are using
version control tools (Visual Source Safe)
d) Level – 0 (Sanity / Test Acceptance / Build verification test):
After receiving initial build, Testing Engineers concentrate on basic functionality of
that build to estimate stability for complete testing. In this Sanity testing, Testing Engineers
tries to execute all P0 Test Cases to cover basis functionality. If functionality is not working /
functionality missing, Testing team rejects that build. If Tester decided stability then they
concentrate on Test execution of all Test Cases to detect defects.
During this Sanity testing, Testing Engineer observes below factors on that build
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 25
26. gcrindia@gmail.com
1) Understandable
2) Operatable
3) Observable
4) Consistency
5) Controllable
6) Simplicity
7) Maintainable
8) Automation
From the above “8” testable issues, Sanity test is also known as Testability testing /
OCT angle testing.
e) Test Automation:
If test automation is possible than Testing team concentrate on Test script creation
using corresponding testing tools. Every Test script consists of navigation statement along
with required check points.
Stable Build
Test Automation
(Select Automation)
(All P0 & Carefully selected P1 Test Cases)
f) Level – 1 (Comprehensive testing)
After completion of Sanity testing & possible test automation, Testing team
concentrates on test batches formation with depended Test Cases. Test batches are also
known as Test suits / sets. During these Test batches execution, Test Engineers prepare test
log document, this document consist of three types of entries.
1) Passed (Expected = Actual)
2) Failed (Any one Expected != Actual, Any one Expected variants from Actual)
3) Blocked (Corresponding parent functionality failed)
Pass
Skip
In queue In Progress Fail Closed
Blocked Partial
Pass / Fail
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 26
27. gcrindia@gmail.com
g) Level – 2 (Regression testing)
During Comprehensive test execution, Test Engineers are reporting mismatches as
defects to developers. After receiving modified build from developers, Test Engineers
concentrate on Regression testing to ensure bug-fixing work & occurrences of side effects.
Resolved Bug Severity
Low Medium High
Case I:
If development team resolve bugs severity which is high, Test Engineers re-execute
all P0, P1 & carefully selected P2 Test Cases on modified build
Case II:
Bugs severity is medium, then all P0, carefully selected P1 & some of P2 Test Cases
Case III:
Bugs severity is low, then some P0, P1 & P2
Case IV:
If development team released modified build due to sudden changes in project
requirement then Test Engineers re-execute all P0, P1 & carefully selected P2 Test Cases w.r.t
that requirement modification.
h) Level – 3 (Final Regression / Pre-Acceptance testing)
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 27
28. gcrindia@gmail.com
Gather Regression
Requirement
Test Reporting Effort Estimation
Final Regression Plan Regression
7) TEST REPORTING:
Level - 0
Level - 1
Test Reporting
Level - 2
Level - 3
During comprehensive testing, Test Engineer are reporting mismatches as defects to
developers through IEEE format.
1) Defect ID: Unique No or Name
2) Description: Summary of the defect
3) Feature: Module / Function / Service , in these module TE found the defect
4) Test Case Name: Corresponding failing test condition
5) Reproducible (Yes / No): Yes -> Every time defect appears during test execution
No -> Rarely defect appears
6) If Yes, attach test procedure:
7) If No, attach snapshot & strong reasons:
8) Status: New / Reopen
9) Severity: Seriousness of defect w.r.t functionality (high / medium / low)
10) Priority: Importance of the defect w.r.t customers (high / medium / low)
11) Reported bug: Name of Test Engineer
12) Reported on: Date of submission
13) Assign to: Name of the responsible person in development team -> PM
14) Build Version ID: In which build, Test Engineer fount the defect
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 28
29. gcrindia@gmail.com
15) Suggested fix (Optional): Tester tries to produce suggestion to solve this defect
16) Fixed by: PM or Team Lead
17) Resolved by: Developer name
18) Resolved on: Date of solving By Developers
19) Resolution type: check out in next page
20) Approved by: Signature of Project Manager (PM)
Defect Age: The time gap between “reported on” & “resolved on”
Defect submission process:
Quality Project Mgr
Analyst Test Mgr
Team Lead
Test Lead
If high defect
is rejected
Developer
Test Eng
Defect Status Cycle:
New Open / rejected / deferred close reopen
Deferred => Accepted but not interested to resolve in this version
Defect Resolution:
After receiving defect report from Testers, developers review the defect & they send
resolution type to Tester as a reply
1) Duplicate, rejected due to the defect is same as previously reported defect
2) Enhancement, rejected due to the defect is related future requirement of customer
3) H/w limitation, rejected due to the defect raised w.r.t limitation of H/w devices
4) S/w limitations, rejected due to the defect raised w.r.t limitation of S/w Techno
5) Not applicable, rejected due to the defect has no proper meaning
6) Functions as designed, rejected due to coding is correct w.r.t to designed doc’s
7) Need more information, not (accepted / rejected) but developers requires extra
information to understand the defect
8) Not reproducible, not (accepted / rejected) but developers require correct
procedure to reproduce the defect
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 29
30. gcrindia@gmail.com
9) No plan to fix it, not (accepted / rejected) but developers want extra time to fix
10) Fixed, developers accepted to resolve
11) Fixed indirectly, accepted but not interested to resolve in this version (default)
12) User misunderstanding, need extra negotiation between testing & development
team.
Types of defects:
01) User Interface bugs (low severity):
1) Spelling mistakes (high priority)
2) Improper alignment (low priority)
02) Boundary related bugs (medium severity)
1) Doesn’t allows valid type (high priority)
2) Allows invalid type also (low priority)
03) Error handling bugs (medium severity)
1) Doesn’t providing error message window (high priority)
2) Improper meaning of error message (low priority)
04) Calculations bugs (high severity)
1) Final output is wrong (low priority)
2) Dependent results are wrong (high priority)
05) Race condition bugs (high severity)
1) Dead lock (high priority)
2) Improper order of services (low priority)
06) Load conditions bugs (high severity)
1) Doesn’t allow multiple users to access / operate (high priority)
2) Doesn’t allow customers accepted load (low priority)
07) Hardware bugs (high severity)
1) Doesn’t handle device (high priority)
2) Wrong output from device (low priority)
08) ID control bugs (medium severity)
1) Logo missing, wrong logo, Version No mistake, Copyright window missing,
Developers Name missing, Tester Name missing
09) Version control bugs (medium severity)
1) Differences between two consecutive build versions
10) Source bugs (medium severity)
1) Mistake in help documents – Manual support
8) TEST CLOSURE:
After completion of all possible test cycle execution, Test Lead conducts a review to
estimate the completeness & correctness of testing. In this review, Test Lead follows below
factors with Test Engineers
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 30
31. gcrindia@gmail.com
1) Coverage Analysis
a) BR based coverage
b) Use Cases based coverage
c) Data model based coverage
d) User Interface based coverage
e) TRM based coverage
2) Bug density
a) Module A has 20% percentile bugs found
b) Module B has 20% percentile bugs found
c) Module C has 40% percentile bugs found
d) Module D has 20% percentile bugs found
3) Analysis of deferred bugs
Whether deferred bugs are deferrable or not
At the end of this review, Testing team concentrate on high bug density modules or
all modules if time is available.
9) User Acceptance Testing (UAT)
Organization management concentrate on UAT to collect feedback, there are two
approaches to conduct testing.
1. Alpha (α) test
2. Beta (β) test
10) Sign Off
After completion of User Acceptance testing & their modifications, Test Lead
concentrates on final test summary report creation. It is a part of Software Release Node (S/
w RN). This final test summary report consist of below documents
1) Test Strategy / Methodology (TRM)
2) System Test Plan
3) Requirement Traceability Matrix (RTM)
4) Automated Test Scripts
5) Bugs Summary Reports
The below, has to be in horizontal direction
• Bug Description
• Feature
• Found By
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 31
32. gcrindia@gmail.com
• Status (closed / deferred)
• Comments
CASE STUDY ON A PROJECT TESTING PROCESS
The “ X ” is a client/server product. It is running in single computer with windows 2000
as OS this product provides a facility to search matched records in existing database. w.r.t
has given search keys.
Local host
client DSN DB
Windows 2000
This product maintains a default administrator to create new users and every valid
user search data in database.
Activity flow diagram: -
Login
Admin Admin Invalid
(Or) user
Valid user
New Search Re-login
user records
Search keys
Existing DB
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 32
33. gcrindia@gmail.com
FUNCTIONAL POINTS: -
Login is taking user id and password
User id and password allows alphabets in lower case from 4 to 8 characters long.
New user id’s created by administrators only
New user creation windows allows unique user id and password with create and
cancel buttons
“Search records” opened for valid users only
“Search records window” maintains below search keys
Customer id: 6 digits number (collected from design document
First name: one character in upper or lower
Last name: one to eight characters in lower case characters
Date of birth: ddmmyy in numeric
Age: “from” and “to” in numeric
Search records windows allows below combination of fields to search records.
→ Last name
→ Last with first name
→ Last name with first name and d-o-b
→ Last name with first name and age
→ Customer id only
“Search records” window consists of “start search” and “stop search” buttons.
Allows last name as full or partial
Allows customer id as full or partial with * or wild card
Customer id
2 8 6 * ------
286*-----
Refresh search records window using Alt+ctrl
Display matched records in a pop-up window with ok button after search
completion.
Returns message like “too many matches to display when matched records >1000
Test methodology:- (by PM)
Testing stage System testing
Testing Factors
Authorization √
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 33
34. gcrindia@gmail.com
Access Control √
Audit trail ×
Continuity to √
Correctness √
Coupling ×
Data integrity √
Ease of use √
Ease of operate √
Reliability √
Fortable ×
Performance ×
Service levels √
Maintainable √
Methodology √
Note: Test responsibility matrix for IIXI (11 by 1)
“X” product is maintaining metadata so
it is not sharing resources of other application
This application went to run on windows 2000
It is a stand alone application (at time one user can operate)
So need net to test load and stress testing)
System test plan by test lead:-
1. Test plan ID: STP_X
2. Introduction: “X” is a product and it provides a facility to connect to existing data
base and search matching records to retrieve.
3. Test items → user creation
→ Login by user
→ Search records
4. Features to be tested: → user creation
→ Login by user
→ Search records
5. Features not to be tested:-
6. Approach: To apply PM selected 1 factors from TRM, below black box testing
techniques are suitable to follow depends on test lead.
→ User interface testing
→ Manual support testing
→ Functionality testing
→ i/p domain testing
→ Recovery testing
→ Sanitation testing
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 34
35. gcrindia@gmail.com
→ Installation testing
→ Security testing
→ Complaints testing
7. Entry criteria: -
→ Are the necessary documents available?
→ Is the “X” product is ready for release from developers?
→ Is the supporting database available to search required records?
→ Is the test environment ready?
8. Suspension criteria:
→ Data base disconnect may require suspension of testing
→ Suspension of testing is mandatory when searching records process went to
infinite.
→ Admin is failed to new user creation, a decision can be mad to continue testing
on “searching records” module using admin or other existing valid users.
9. Exit Criteria: -
→ Ensure that the “X” product provides the required services
→ Ensure that all test documents has been completed up to date.
→All high severity bugs resolved.
10. Test deliverables:-
Test cases
Test procedures Test Engg..
Automated Test scripts
Test log
Defect Report
11. Test environment:-
→ Client pc or local host
→ OS: Win2000
→ DB server: ORACLE/ SQL SERVER/ MS-ACCESS
→ Connectivity: DSN/ Thin Drivers
12. Testing Tasks:-
→ Availability of admin with password
→ Database consists of records
→ Valid users are able to database to search records
13. Staff and Training needs:-
Test Engg.. / QA Engg: Kurugonda Srinaiah
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 35
36. gcrindia@gmail.com
14. Responsibilities:
Document / Report Responsibility Effort
1. Tst cases with procedures K.Srinaiah 12 hours
Defect Report K Srinaiah every day during
Testing
Test completion reports Test Lead with At the end of the
Testing
K Srinaiah
15. Schedule:
Task Effort Start date
End date
Test design 12 hours 28-12-2005
29-12-2005
Implement test and 4 hours 29-12-2005
29-12-2005
Review
Execute test 24 hours 30-12-2005
01-01-2006
Evaluate test 8 hours 02-01-2006
02-01-2006
16. Risks and mitigations:-
1. Lack of documentation:
→ Contact business analyst
→ Ad-hoc testing
→ Contact customer site people if possible
2. Lack of time
→ Over-time
3. Delays and delivery:
→ Over time
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 36
37. gcrindia@gmail.com
4. Lack of development process reggur:
→ Contact test lead to motivate developers
→ Over time to complete task is right time
17. APPROVALS: -
Test case 1:
Signature of PM and signature of test lead.
Test case 2: Successful entry of user id
BVA (size)
Min = 4 chars → pass
Max = 8 chars→ pass
Min-1 =3 chars → fail
Min +1 = 5 chars → pass
Max –1 = 7 chars → pass
Max +1 = 9 chars → fail
Test case 3: successful entry of password
BVA (size)
Min = 4 chars → pass
Max = 8 chars → pass
Min –1 = 3 chars → fail
Min +1 = 5 chars → pass
Max + = 7 chars → pass
Max = 9 chars → fail
Test case 4: successful login operation
User id Password Criteria
Admin valid pass
Admin invalid fail
Other valid valid pass
Other valid invalid fail
Other invalid invalid fail
Blank value fail
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 37
38. gcrindia@gmail.com
Valid blank fail
Test case 5: Successful selection of new user creation option
Test case 6: Un successful selection of this option due to current user is not admin.
Test case 7 successful entry of user id in create user window
Note: (like as Test case2)
Test case 8: Successful entry of userid in create user window
Note: (-----------test case 3)
Test case9: Successful creation of new user by admin
Test case10: unsuccessful new user creation due to given user id is not unique.
Test case 11: successful closing of new user creation window using cancel
(After enter user id and offer enter passes)
Test case 12: Successful selection of search records option
Test case 13: successful entry of customer id
BVA (size) ECP (TYPE)
Min = max = 6 valid invalid
--------------------------
0 – 9 a-z, A-Z, special characters
Expect * , blank space
Start with *
Exp: 123 √, *23Х,
1*23X
Test case 14: successful entry of first name
Min = max = 1 → pass Ecp
---------------------------
o √ fail valid invalid
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 38
39. gcrindia@gmail.com
----------------------------
a- z o-9,
A-Z special characters
Test case 15: successful entry of last name:
Min = 1 and max = 8 → pass ----------------
valid invalid
-----------------
a- z A-Z, o-9,
Special characters
Test case 16: successful entry of DOB
BVA (range)
Ecp (type)
Day: min → 01 -----------------
min → 31 valid invalid
-----------------
0- 9 a-z, A-Z
Month: min → 01 special characters
max→ 12
Year: min → 00
max→ 99
Case 17: success entry of age from
Ecp(type)
min → 01 -----------------
max→ 22 valid invalid
-----------------
0- 9 a-z, A-Z
Special characters
Test case 18: successful entry of age to
Note: like as above
Test case 19: successful display of matched records with full last name and all other
fields are
Blank
Test case 20: successful display of matched records with full last name and first name
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 39
40. gcrindia@gmail.com
Test case21: successful display of matched records with full last name first name and dob
Test case22: successful display of matched records with full last name first name age
Test case 23: on successful search operation due to invalid combination of filled fields.
Test case 24: unsuccessful search operation due to invalid Dob
Test case 25: unsuccessful search operation due to age from greater than age ‘To’
Test case26: successful display of records with search key as partial last name and other
fields
as blank
Test case 27:successful display of records with search key a partial last name and first
name
Test case 28: successful display of records with search key as partial last name, first name
and
Dob
Test case 29: successful display of records with search key as partial last name, first name
Test case 30: successful display of records with search key as customer id
Test case 31: successful display of records with search key as partial customer id with *
as
wild card
Test case 32: Unsuccessful display of records due to no matching records in database
w.r.to
given search keys
Test case 33: unsuccessful display of records due to “too many” records to display when
no
of matched records greater than 1000
Test case 34 : successful refresh search window with Alt +Ctrl
Test case 35: Successful termination of search operation when click “stop search” button.
Test case 36: successful closing of records window through click o.k after searching.
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 40
41. gcrindia@gmail.com
Test case 37: spelling check in every screen
Test case 38: Graphics check in every screen
Ex: (alignment, font, size, label, graphical, colour, etc)
Usability
Testing
Test case39: Accuracy of data displayed
Ex:Dob ddmmyy
Test case 40: Meaninful help messages and error messages
G.C.Reddy, QTP Trainer, Hyderabad (9247837478) 41