The document contains responses to questions about software testing terms and concepts. Key points discussed include:
- Cyclomatic complexity is a white box testing type that analyzes the complexity of code.
- Monkey testing tests software without test cases by randomly interacting with screens and inputs to find bugs.
- Severity refers to a bug's seriousness while priority refers to which bug should be fixed first.
- A login screen bug example is provided where severity is low but priority is high due to usability issues.
- System testing is a type of black box testing that tests the full application and includes functionality, regression, and performance testing.
A presentation on software testing importance , types, and levels,...
This presentation contains videos, it may be unplayable on slideshare and need to download
The document discusses testing best practices for rich client applications. It outlines the challenges of testing user interfaces and interactions. It then describes different levels of testing from ad hoc to crowdsourcing. Unit testing, continuous integration, and automated functional testing are explained. The current state of testing tools for Titanium is presented along with a demo. Future directions including more automation and crowdsourced testing are envisioned.
The document provides answers to various questions related to manual software testing practices. It discusses key concepts like priority and severity levels of defects, examples of high severity low priority defects. It also covers the basis for test case review, contents of requirements documents, differences between web and client-server application testing, defect life cycle, and techniques for test plan preparation. The document is a guide for manual testers that aims to enhance their understanding of software testing concepts and best practices.
The document provides an overview of software testing basics, including definitions of key terms like testing, debugging, errors, bugs, and failures. It describes different types of testing like manual testing, automation testing, unit testing, integration testing, system testing, and more. It also covers test planning, test cases, test levels, who should test, and the importance of testing in the software development life cycle.
Software testing is the process of evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. Software testing is a process that should be done during the development process. In other words software testing is a verification and validation process.
Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a computer program/application/product:
• meets the requirements that guided its design and development,
• works as expected,
• can be implemented with the same characteristics,
• and satisfies the needs of stakeholders.
Software Development Process Cycle:-
PLAN (P): Device a plan. Define your objective and determine the strategy and supporting methods required to achieve that objective.
DO (D): Execute the plan. Create the conditions and perform the necessary training to execute the plan.
CHECK (C): Check the results. Check to determine whether work is progressing according to the plan and whether the results are obtained.
ACTION (A): Take the necessary and appropriate action if checkup reveals that the work is not being performed according to plan or not as anticipated.
Testbytes is a community of software testers who are passionate about quality and love to test. We develop an in-depth understanding of the applications under test and include software testing strategies that deliver quantifiable results.
In short, we help in building incredible software.
Testing is the process of validating and verifying software to ensure it meets specifications and functions as intended. There are different levels of testing including unit, integration, system, and acceptance testing. An important part of testing is having a test plan that outlines the test strategy, cases, and process to be followed. Testing helps find defects so the product can be improved.
The document provides information about manual testing interview questions and answers. It discusses key topics like the differences between QA, QC and software testing, when to start QA in a project, definitions of verification and validation and their differences, differences between smoke testing and sanity testing, definition of testware, differences between retesting and regression testing, explanation of bug lifecycle, how severity and priority of bugs are related, definition of regression testing, what bug triage is, types of tests performed on web applications, how to choose which defects to remove, explanation of the testing lifecycle, what constitutes good code, the role of a bug tracking system, what data driven testing is, an explanation of CMM levels, the purpose of testing,
Black box testing tests the functionality of software without knowledge of its internal structure or design. It is performed by testers and clients to test the software from an end user's perspective. There are various techniques used in black box testing including equivalence partitioning, boundary value analysis, and error guessing.
The document contains 30 interview questions for experienced software testers. Some key questions and answers include:
- What is the difference between a Requirements Traceability Matrix and a Test Plan? The RTM ensures requirements remain the same throughout development while the Test Plan describes the scope, approach, resources and schedule for testing.
- When should automated testing be chosen over manual testing? Automated testing is preferred when test cases are frequently used, automation scripts can run faster than manual execution, scripts can be reused, and test cases are suitable for automation.
- What are some of the main challenges in software testing? Challenges include unstable applications, tight timelines, understanding requirements, limited resources and tools, and changing
Students are struggling in Software Testing so i have decided to make a presentation on Testing here is the general topic from testing. I hope it will help you in your learning about testing please rate it
The document discusses software testing concepts including:
- Quality assurance ensures processes are established to produce products that meet specifications.
- Testing determines if a product meets requirements and identifies failures to meet requirements.
- A test plan is written by the lead tester and includes the testing strategy, resources, and plans. It outlines test cases and procedures to validate software meets specifications.
- Testing begins in the define system phase to ensure requirements are testable, and continues through subsequent phases including product testing, acceptance testing, and deployment. Documentation and repeatable processes are critical to quality assurance.
** Software Testing Certification Courses: https://www.edureka.co/software-testi... **
This Edureka PPT on Types of Software Testing covers the various types of functional and non-functional testing. Below topics are covered in this PPT:
What is Software Testing
Why need Testing?
Software Testing Life Cycle
Types of Software Testing
Unit Testing
Integration Testing
System Testing
Interface Testing
Regression Testing
Acceptance Testing
Documentation Testing
Installation Testing
Performance Testing
Reliability Testing
Security Testing
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
This document contains 151 interview questions related to software testing. The questions cover a wide range of testing topics including definitions of software testing, the difference between various testing types, the testing process, test planning and documentation, defect management, and other quality assurance and development processes. Responses would require in-depth knowledge of software testing practices, tools, and methodologies.
With a pre-requisite of ensuring an application's flawless functioning, this PPT sheds light on what functional testing entails with its importance to enhance an application's quality. Get to know more on Functional Testing Services, Functional Testing Types, Smoke Testing, Sanity Testing, Regression Testing with this presentation and stay tuned for our upcoming ones.
1. The document provides multiple choice questions related to software testing concepts and terms. It covers topics like test case design, test levels, defect management, risk analysis, test techniques and tools.
2. Several questions test knowledge of terms related to test coverage, test types, integration testing techniques, defect prioritization and analysis. Other topics assessed include test planning, test metrics, compatibility testing and quality perspectives.
3. The document contains 75 multiple choice questions to evaluate understanding of key software testing concepts and best practices. The breadth of topics covered provides a comprehensive skills assessment.
This document discusses software engineering and software testing. Software engineering is concerned with developing large software through applying engineering principles. The challenge is to produce high quality software within budget and schedule constraints. Software testing is the process of finding errors in software and involves both manual and automated testing. Different types of testing include unit, integration, system, and acceptance testing. The goal of testing is to uncover defects early and reduce costs.
This document provides an overview of manual software testing interview questions and answers. It discusses key terms like bugs, errors, defects, and different types of testing such as white box testing, black box testing, compatibility testing, and the V-model framework. Specific questions covered include what stubs and drivers are, explaining test cases, test suites, and the different phases of the software testing life cycle. The document also provides answers to questions about test techniques like boundary value analysis, equivalence partitioning, and test coverage criteria like statement coverage.
A brief that includes the following:
- Software Testing
- Quality Assurance
- Quality Control
- Types of Testing
- Levels of Software Testing
- Types of Performance Testing
- API
- Verification & Validation
- Test Plan & Testing Strategy
- Agile & Waterfall
- Software Development Life Cycle
- Career Path
A presentation on software testing importance , types, and levels,...
This presentation contains videos, it may be unplayable on slideshare and need to download
The document discusses testing best practices for rich client applications. It outlines the challenges of testing user interfaces and interactions. It then describes different levels of testing from ad hoc to crowdsourcing. Unit testing, continuous integration, and automated functional testing are explained. The current state of testing tools for Titanium is presented along with a demo. Future directions including more automation and crowdsourced testing are envisioned.
Manual testing interview question by INFOTECHPravinsinh
The document provides answers to various questions related to manual software testing practices. It discusses key concepts like priority and severity levels of defects, examples of high severity low priority defects. It also covers the basis for test case review, contents of requirements documents, differences between web and client-server application testing, defect life cycle, and techniques for test plan preparation. The document is a guide for manual testers that aims to enhance their understanding of software testing concepts and best practices.
The document provides an overview of software testing basics, including definitions of key terms like testing, debugging, errors, bugs, and failures. It describes different types of testing like manual testing, automation testing, unit testing, integration testing, system testing, and more. It also covers test planning, test cases, test levels, who should test, and the importance of testing in the software development life cycle.
Software testing is the process of evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. Software testing is a process that should be done during the development process. In other words software testing is a verification and validation process.
Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to the process of executing a program or application with the intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a computer program/application/product:
• meets the requirements that guided its design and development,
• works as expected,
• can be implemented with the same characteristics,
• and satisfies the needs of stakeholders.
Software Development Process Cycle:-
PLAN (P): Device a plan. Define your objective and determine the strategy and supporting methods required to achieve that objective.
DO (D): Execute the plan. Create the conditions and perform the necessary training to execute the plan.
CHECK (C): Check the results. Check to determine whether work is progressing according to the plan and whether the results are obtained.
ACTION (A): Take the necessary and appropriate action if checkup reveals that the work is not being performed according to plan or not as anticipated.
Testbytes is a community of software testers who are passionate about quality and love to test. We develop an in-depth understanding of the applications under test and include software testing strategies that deliver quantifiable results.
In short, we help in building incredible software.
Testing is the process of validating and verifying software to ensure it meets specifications and functions as intended. There are different levels of testing including unit, integration, system, and acceptance testing. An important part of testing is having a test plan that outlines the test strategy, cases, and process to be followed. Testing helps find defects so the product can be improved.
The document provides information about manual testing interview questions and answers. It discusses key topics like the differences between QA, QC and software testing, when to start QA in a project, definitions of verification and validation and their differences, differences between smoke testing and sanity testing, definition of testware, differences between retesting and regression testing, explanation of bug lifecycle, how severity and priority of bugs are related, definition of regression testing, what bug triage is, types of tests performed on web applications, how to choose which defects to remove, explanation of the testing lifecycle, what constitutes good code, the role of a bug tracking system, what data driven testing is, an explanation of CMM levels, the purpose of testing,
Black box testing tests the functionality of software without knowledge of its internal structure or design. It is performed by testers and clients to test the software from an end user's perspective. There are various techniques used in black box testing including equivalence partitioning, boundary value analysis, and error guessing.
30 testing interview questions for experienceddilipambhore
The document contains 30 interview questions for experienced software testers. Some key questions and answers include:
- What is the difference between a Requirements Traceability Matrix and a Test Plan? The RTM ensures requirements remain the same throughout development while the Test Plan describes the scope, approach, resources and schedule for testing.
- When should automated testing be chosen over manual testing? Automated testing is preferred when test cases are frequently used, automation scripts can run faster than manual execution, scripts can be reused, and test cases are suitable for automation.
- What are some of the main challenges in software testing? Challenges include unstable applications, tight timelines, understanding requirements, limited resources and tools, and changing
Students are struggling in Software Testing so i have decided to make a presentation on Testing here is the general topic from testing. I hope it will help you in your learning about testing please rate it
The document discusses software testing concepts including:
- Quality assurance ensures processes are established to produce products that meet specifications.
- Testing determines if a product meets requirements and identifies failures to meet requirements.
- A test plan is written by the lead tester and includes the testing strategy, resources, and plans. It outlines test cases and procedures to validate software meets specifications.
- Testing begins in the define system phase to ensure requirements are testable, and continues through subsequent phases including product testing, acceptance testing, and deployment. Documentation and repeatable processes are critical to quality assurance.
** Software Testing Certification Courses: https://www.edureka.co/software-testi... **
This Edureka PPT on Types of Software Testing covers the various types of functional and non-functional testing. Below topics are covered in this PPT:
What is Software Testing
Why need Testing?
Software Testing Life Cycle
Types of Software Testing
Unit Testing
Integration Testing
System Testing
Interface Testing
Regression Testing
Acceptance Testing
Documentation Testing
Installation Testing
Performance Testing
Reliability Testing
Security Testing
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
This document contains 151 interview questions related to software testing. The questions cover a wide range of testing topics including definitions of software testing, the difference between various testing types, the testing process, test planning and documentation, defect management, and other quality assurance and development processes. Responses would require in-depth knowledge of software testing practices, tools, and methodologies.
With a pre-requisite of ensuring an application's flawless functioning, this PPT sheds light on what functional testing entails with its importance to enhance an application's quality. Get to know more on Functional Testing Services, Functional Testing Types, Smoke Testing, Sanity Testing, Regression Testing with this presentation and stay tuned for our upcoming ones.
1. The document provides multiple choice questions related to software testing concepts and terms. It covers topics like test case design, test levels, defect management, risk analysis, test techniques and tools.
2. Several questions test knowledge of terms related to test coverage, test types, integration testing techniques, defect prioritization and analysis. Other topics assessed include test planning, test metrics, compatibility testing and quality perspectives.
3. The document contains 75 multiple choice questions to evaluate understanding of key software testing concepts and best practices. The breadth of topics covered provides a comprehensive skills assessment.
QSpiders - Selenium Webdriver Syllabus to meet growing skill demands of the current job market. Here is all new Selenium WebDriver course covering concepts from basics to advance test automation.
The document discusses automation testing using Selenium. It provides an overview of Selenium, including what it is, its components like Selenium IDE, Selenium RC, Selenium Grid, and Selenium WebDriver. It explains the features and advantages of each component. Selenium is an open source tool that allows automated testing of web applications across different browsers and platforms. It supports recording and playback of tests and can help reduce testing time and costs through automation.
This document contains a chapter summary and self-check quiz about software project planning. Some key points:
- The objective of software project planning is to enable managers to reasonably estimate costs and schedules. Project scope defines system functionality, performance, costs, resources, schedule and milestones.
- Determining project feasibility considers business/marketing concerns, scope/constraints/market, technology/finance/time/resources. External interfaces must be evaluated.
- Estimating team size is done after estimating development effort. Reusable components must be catalogued, standardized and validated for easy integration.
- Estimation techniques include empirical models, white-box methods, and regression models. Size estimates cannot be solely based on LOC
Manual testing is the process of manually testing software for defects by playing the role of an end user and using all features of the application to ensure correct behavior, following a written test plan. The document discusses various concepts related to manual testing including software quality assurance, verification, validation, software life cycles, testing techniques like black box testing and white box testing, unit testing, alpha testing, beta testing, system testing, volume testing, stress testing, and security testing. It provides brief definitions and purposes of these concepts.
ISTQB Foundation level Sample Paper - Part 3 Parul Chotalia
The document appears to be a sample question paper for an ISTQB Foundation level certification. It contains 38 multiple choice questions testing various concepts in software testing such as test levels, test techniques, test documentation, test management and test process. The questions cover topics like test planning, test design, test execution, incident management and test types.
Software testing quiz questions and answersRajendraG
This document contains a software testing quiz with 77 multiple choice questions covering various topics in software testing. The questions assess knowledge in areas such as test documentation, test types, quality management, testing levels, metrics, risks, and the software development life cycle. Correct answers are provided at the end. The quiz is intended to help individuals learn and evaluate their understanding of key concepts in software testing.
The document discusses the OSI model and networking layers. It provides details on the functions of each layer, including physical, data link, network, transport, session, presentation and application layers. Key points covered include how each layer works independently and interfaces with adjacent layers, common protocols and services used at each layer, and how network devices operate at certain layers to enable communication.
What is data and information? What is data base? What is data base management system? What are various data base models??? Components of data base function of data base. Advantages of data base. And what is system language query???
Basic Data Management Concept
Organizing Data in a Database
Database Management Systems
Software, Types of Software
Software Project, Application and Product
Software Business Process
SDLC
SDLC Models
Test Levels
Software Environment
Test Types
Test Design Techniques
Testing Process (STLC)
Informal Testing
Quality Standards
Software Business Domains
Data is a useful information
Which helps to make a decision
Set of information of any entity is known as data
Databases support storage and manipulation of data
Interest Assignments
Partnership Assignments
Percentages Assignment
Profit and Loss
Assignments
Proportion Assignments
Set Theory Assignments
Time and Distance Assignments
Time and Work Assignments
Permutation Assignments
Allegation Assignments
AP,GP Assignments
Istqb intro with question answer for exam preparationKevalkumar Shah
The document provides an overview of software testing concepts including definitions of software testing, who can perform testing, common terminology, the software development life cycle (SDLC), testing methods and levels, and more. It defines software testing as the process of comparing expected and actual results to identify defects. It outlines the typical stages of the SDLC as initial, analysis, design, coding, testing, and delivery/maintenance phases. It also describes black box, white box, and grey box testing methods and the five levels of testing: unit, module, integration, system, and acceptance.
The document provides sample answers to common software testing interview questions. It begins with introducing oneself, including education, experience, and strong points. It then discusses responsibilities as a QA engineer or leader. Other questions and answers cover strong and weak points, reasons for changing jobs, knowing when testing is enough, when testing should stop, estimating testing time, challenges faced, and achievements. The document provides guidance on working under pressure.
This document provides an overview of fundamentals of software testing. It discusses the five parts of the fundamental test process in broad chronological order: planning and control, analysis and design, implementation and execution, evaluating exit criteria and reporting, and test closure activities. It also covers topics like regression testing, confirmation testing, the differences between re-testing and regression testing, and the importance of independence in testing.
Intro to Unit Testing with test Driven DevelopmentJoel Cochran
Test Driven Development is a technique that requires Unit Tests for code to be written before the code itself. By placing the emphasis on testing, developers can define success before code is written. This helps us answer that elusive question of "when is code done?" TDD offers additional benefits such as only writing code you need to satisfy your requirements (YAGNI), and enhanced maintainability.
The document discusses various topics relating to software project management including:
- Defining defect prevention as avoiding defect insertion.
- Stating that the main goal of quality assurance is to reduce risks in developing software.
- Indicating that requirements must be unambiguously stated.
- Noting that effective software project management focuses on people, process, product, and project.
Software Testing and Quality Assurance Assignment 2Gurpreet singh
The document discusses various software testing concepts and terms. It contains 10 short questions with explanations of stress testing, cyclomatic complexity, object oriented testing, regression testing, loop testing vs path testing, client server environment, graph based testing, security testing benefits, characteristics of real-time systems, and benefits of data flow testing. It also includes 4 longer questions about designing test cases, discussing factors for testing a real-time system, testing in a multiplatform environment, and explaining graph based testing in detail.
Black-box testing views the program as a black box without seeing code. White-box testing examines internal structure. Gray-box combines black-box and knowledge of database validation. Test scripts are sets of automated instructions. Test suites are collections of test cases or scripts. Stress testing subjects a system to unreasonable loads to find breaking points while load testing uses representative loads.
- "Testing is the process of executing a program with the intent of finding faults."
- Good testing involves more than just executing a program a few times, including testing all possible paths and inputs. However, exhaustive testing of everything is impossible due to constraints.
- The costs of fixing errors increases drastically from early phases like specification to later phases like testing and maintenance. Early testing helps find errors at lower cost.
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flexmichael.labriola
This document discusses automated testing in Flex. It begins by explaining why automated testing is important, such as reducing costs from software errors and allowing developers to change code without fear of breaking other parts of the project. It then covers topics like writing unit tests, using theories and data points to test over multiple values, and writing integration tests. The document emphasizes that writing testable code is key, and provides some principles for doing so, such as separating construction from application logic and using interfaces. It also discusses using fakes, stubs and mocks to isolate units for testing.
The document discusses various software testing techniques including black box testing, white box testing, and grey box testing. It provides details on specific techniques such as equivalence partitioning, boundary value analysis, statement coverage, condition coverage, function coverage, and cyclomatic complexity. The objective is to understand these techniques so they can be used effectively to test applications and find defects.
The document discusses testing and debugging software. It describes the purpose of testing as ensuring software is fit for purpose by meeting specifications and is robust and reliable. Various types of tests are described, including normal, extreme, and exceptional test data and inputs. The importance of systematic and comprehensive testing is emphasized. Debugging techniques like dry runs, trace tables, breakpoints, and watchpoints are introduced to help identify bugs in software.
1. Create test classes for each item type (book, food, medical, imported, etc.) and calculate tax amounts
2. Write test methods that pass sample baskets of items to the calculation method and assert the expected tax and total amounts are returned
3. Include test cases that validate tax rounding is performed correctly for different tax rates and item prices
4. Write exception tests to ensure invalid item types or negative prices throw the expected exceptions
This document discusses unit testing and its benefits. It begins by outlining some questions about unit testing, then compares unit tests to UI tests. Unit tests are faster, test individual functions, and make code easier to change and refactor. The document provides an example of unit testing a password validation function in PHP Laravel. It discusses that while test coverage is a quality metric, high coverage alone does not guarantee high quality. It argues that internal quality through practices like unit testing does not require tradeoffs with development speed, and can actually improve productivity by reducing unnecessary tasks and lead time. Maintaining clean code through practices like unit testing is important for both quality and speed.
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
This document discusses test-driven development (TDD), including what it is, why it is used, and how to implement it. TDD is a development approach where small test cases are written before code to validate requirements, with code written only to pass failing tests. It is a philosophy of workflow and design that helps clarify expectations, validate system state through assertions, break problems into smaller pieces, and protect against regressions. The process involves writing a single small test, writing just enough code to make it pass, thinking of other inputs and edge cases, and using mocks to stand in for external resources when testing relationships between code units.
The document provides answers to various manual testing questions and examples. It discusses key concepts like priority and severity, examples of high severity low priority defects and vice versa. It also covers test case review criteria, contents of requirements documents, differences between web and client-server testing, test plan contents, defect lifecycle, regression testing approach, and how to report defects in an excel sheet.
Manualtestinginterviewquestionbyinfotech 100901071035-phpapp01Anshuman Rai
The document provides information about manual software testing concepts including priority and severity levels, examples of high severity low priority defects, bases for test case review, contents of requirements documents, differences between web and client-server testing, and bug lifecycles. It also includes answers to common testing questions and examples of test cases for a basic calculator application.
Manual testing interview questions by infotech suhasreddy1
The document provides information about manual software testing practices including definitions of priority and severity for defects, examples of high severity low priority defects, bases for test case review, contents of requirements documents, differences between web application and client server testing, examples of defect reporting, bug lifecycles, and approaches to regression testing. Key details covered include assigning priority by developers and severity by testers, focusing regression testing on modules impacted by fixes, and updating test cases based on changes to functionality or code.
Here is one way to drill down from the business requirements to test scripts for an ATM example:
Business Requirement:
- "ATM must do withdrawals"
Test Requirement:
- The ATM should allow a user to withdraw cash within the allowed limits.
Test Scenarios:
1. Valid withdrawal within limits
2. Withdrawal exceeds daily limit
3. Withdrawal is not a multiple of $20
4. Withdrawal amount is less than minimum ($20)
5. Withdrawal amount is greater than maximum ($300)
Test Procedure/Script:
1. Valid withdrawal
a. Insert card
b. Enter pin
c. Select
Nowadays, test automation has become an essential part of testers' lives. However, there are not many resources available for beginners that do not know how to start.
This is why we would like to share their experience and explain the steps followed to develop our test automation framework, including why we've chosen their current testing tools.
The emphasis will be on all the challenges we had to face; the problems we found, our possible solutions and our reasoning for implementing one or the other.
We will share their insight on how to write test scenarios from a functional point of view and how to speed up automated tests through browser initialization.
You will learn which are the steps you have to follow to choose the correct tool and tips & tricks to success in your project.
The document discusses various techniques for software testing including black box testing, equivalence partitioning, boundary value analysis, cause-effect graphing, pairwise testing, and special case testing. The goal of testing is to identify defects by designing test cases that are most likely to cause failures and reveal faults in the software.
An Introduction To Software Development - Test Driven Development, Part 1Blue Elephant Consulting
This presentation is a part of the COP2271C college level course taught at the Florida Polytechnic University located in Lakeland Florida. The purpose of this course is to introduce Freshmen students to both the process of software development and to the Python language.
The course is one semester in length and meets for 2 hours twice a week. The Instructor is Dr. Jim Anderson.
A video of Dr. Anderson using these slides is available on YouTube at:
http://youtu.be/bCp1fbAd56k
Fantastic Tests - The Crimes of Bad Test DesignWinston Laoh
The document discusses why testing is important and what causes bad tests. Testing provides comfort and confidence by knowing if new code breaks existing functionality. Bad tests have a wide scope so it's unclear what they test, depend on specific orders or system states, are too similar to the product without the same fragility, or are not similar enough to the user experience. The key is for tests to be independent of order or system state and balance similarity to the product with enough differences to reliably fail when bugs are present.
Beyond Agile Testing to Lean Development — Rakuten Technology ConferenceJames Coplien
The document discusses moving beyond traditional agile testing approaches to lean testing. It argues that most unit tests are unnecessary and test scenarios that will never occur. It promotes exploratory and experience-based testing over unit testing alone. The document also advocates for shipping tests with code to catch bugs in the field, using assertions to make code more readable, and taking a lean approach where fixing testing processes is prioritized over fixing individual bugs.
The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
The document discusses Infotech's automated testing services including eCATT testing, SAP testing capabilities, and case studies using tools like Mercury, QTP and Load Runner. It provides an overview of Infotech's 60 member SAP team and experience developing test scripts and procedures for clients' business processes. Sample projects are described for United Technologies Research Center involving ABAP development and eCATT, and for Metro Group Information Technology developing automation test scripts using QTP.
Verification and Validation (V&V) are used to ensure software quality. Verification confirms that the software meets its design specifications, while Validation confirms it meets the user's requirements. There are different types of reviews conducted at various stages of development to detect defects early. Reviews include informal peer reviews, semiformal walkthroughs, and formal inspections. Standards help improve quality by providing consistent processes and frameworks for software testing.
The document outlines the key steps in a software testing life cycle including test plan preparation, test case design, test execution and logging, defect tracking, and test reporting. It provides details on each step such as how test plans define the overall testing approach and objectives, test cases define what to test and expected results, and defects identified during testing are tracked, assigned a severity, and prioritized for resolution.
The document discusses various test reporting tools that testers use such as Pareto charts, cause-effect diagrams, and check sheets. It then provides examples of eight interim test reports that provide status updates on functional testing, defects uncovered versus corrected, and average age of uncorrected defects. The summaries provide testing metrics to analyze progress and identify issues.
Static testing examines and reviews software without executing it, while dynamic testing executes the software. There are different types of testing like unit, integration, system, and acceptance testing. Testing techniques include white box, black box, incremental, and thread testing. White box testing examines internal program structure and logic, while black box testing verifies requirements without considering internal structure.
The document provides an overview of manual software testing, including definitions, goals, and best practices. It discusses the importance of testing, what should be tested, quality principles, standards and certifications, the software development life cycle, and roles in the testing process. Testing is defined as evaluating a system to verify requirements or identify differences between expected and actual results. It aims to deliver high quality software by finding errors prior to release. Quality, defined as meeting customer requirements, is crucial and improved through principles like defect prevention. The document outlines the software development process and life cycle from requirement analysis through maintenance.
The document discusses various aspects of project management including planning, scheduling, costing, and monitoring software projects. It also discusses requirement management which involves managing changes to software requirements and using tools like requirement traceability matrices. Configuration management is also covered which deals with version control and tools to manage changes made during a project. Finally, the document discusses software testing including test plans, test cases, classifications of defects, and testing principles.
The document outlines an agenda for testing the functionality, usability, performance, and security of a website. It includes checking links, forms, cookies, database integrity, navigation, content correctness, server-side interfaces, client-side compatibility across platforms and browsers, printing capabilities, response times under different connection speeds and loads, ability to handle stress, login validation, log files, and encryption.
A metric is a quantitative measure that shows the relationship between two variables. Software metrics can measure software, development resources, and processes. There are two types of metrics: process metrics, which measure development methods and tools, and product metrics, which measure documentation and code. Testing metrics include metrics that measure user participation in testing, the extent of testing paths covered, acceptance criteria verified, resources used for testing, and the cost and effectiveness of testing.
QTP is a functional test and regression test automation solution that addresses major software applications and environments. The testing process involves preparation, recording tests, enhancing tests, running and debugging tests, and analyzing results. QTP supports features like checkpoints, parameters, object spying, and keyword-driven testing to simplify test creation and maintenance. It is suitable for functional testing and regression testing of relatively stable systems.
The document provides an overview of key concepts in HP QuickTest Professional (QTP), including:
- QTP allows recording, playback, and enhancement of test scripts. It supports features like checkpoints, output values, and parametrization.
- Object repositories store object properties learned during recording for identification during playback.
- Regular expressions, recovery scenarios, and exception handling help address dynamic objects and errors.
- Functions, file handling, and frameworks can be used to structure tests and interact with external systems.
Best Practices for Effectively Running dbt in Airflow.pdfTatiana Al-Chueyr
As a popular open-source library for analytics engineering, dbt is often used in combination with Airflow. Orchestrating and executing dbt models as DAGs ensures an additional layer of control over tasks, observability, and provides a reliable, scalable environment to run dbt models.
This webinar will cover a step-by-step guide to Cosmos, an open source package from Astronomer that helps you easily run your dbt Core projects as Airflow DAGs and Task Groups, all with just a few lines of code. We’ll walk through:
- Standard ways of running dbt (and when to utilize other methods)
- How Cosmos can be used to run and visualize your dbt projects in Airflow
- Common challenges and how to address them, including performance, dependency conflicts, and more
- How running dbt projects in Airflow helps with cost optimization
Webinar given on 9 July 2024
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
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).
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.
UiPath Community Day Kraków: Devs4Devs ConferenceUiPathCommunity
We are honored to launch and host this event for our UiPath Polish Community, with the help of our partners - Proservartner!
We certainly hope we have managed to spike your interest in the subjects to be presented and the incredible networking opportunities at hand, too!
Check out our proposed agenda below 👇👇
08:30 ☕ Welcome coffee (30')
09:00 Opening note/ Intro to UiPath Community (10')
Cristina Vidu, Global Manager, Marketing Community @UiPath
Dawid Kot, Digital Transformation Lead @Proservartner
09:10 Cloud migration - Proservartner & DOVISTA case study (30')
Marcin Drozdowski, Automation CoE Manager @DOVISTA
Pawel Kamiński, RPA developer @DOVISTA
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
09:40 From bottlenecks to breakthroughs: Citizen Development in action (25')
Pawel Poplawski, Director, Improvement and Automation @McCormick & Company
Michał Cieślak, Senior Manager, Automation Programs @McCormick & Company
10:05 Next-level bots: API integration in UiPath Studio (30')
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
10:35 ☕ Coffee Break (15')
10:50 Document Understanding with my RPA Companion (45')
Ewa Gruszka, Enterprise Sales Specialist, AI & ML @UiPath
11:35 Power up your Robots: GenAI and GPT in REFramework (45')
Krzysztof Karaszewski, Global RPA Product Manager
12:20 🍕 Lunch Break (1hr)
13:20 From Concept to Quality: UiPath Test Suite for AI-powered Knowledge Bots (30')
Kamil Miśko, UiPath MVP, Senior RPA Developer @Zurich Insurance
13:50 Communications Mining - focus on AI capabilities (30')
Thomasz Wierzbicki, Business Analyst @Office Samurai
14:20 Polish MVP panel: Insights on MVP award achievements and career profiling
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
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.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
The Rise of Supernetwork Data Intensive ComputingLarry Smarr
Invited Remote Lecture to SC21
The International Conference for High Performance Computing, Networking, Storage, and Analysis
St. Louis, Missouri
November 18, 2021
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.
RPA In Healthcare Benefits, Use Case, Trend And Challenges 2024.pptxSynapseIndia
Your comprehensive guide to RPA in healthcare for 2024. Explore the benefits, use cases, and emerging trends of robotic process automation. Understand the challenges and prepare for the future of healthcare automation
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
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.
Scaling Connections in PostgreSQL Postgres Bangalore(PGBLR) Meetup-2 - MydbopsMydbops
This presentation, delivered at the Postgres Bangalore (PGBLR) Meetup-2 on June 29th, 2024, dives deep into connection pooling for PostgreSQL databases. Aakash M, a PostgreSQL Tech Lead at Mydbops, explores the challenges of managing numerous connections and explains how connection pooling optimizes performance and resource utilization.
Key Takeaways:
* Understand why connection pooling is essential for high-traffic applications
* Explore various connection poolers available for PostgreSQL, including pgbouncer
* Learn the configuration options and functionalities of pgbouncer
* Discover best practices for monitoring and troubleshooting connection pooling setups
* Gain insights into real-world use cases and considerations for production environments
This presentation is ideal for:
* Database administrators (DBAs)
* Developers working with PostgreSQL
* DevOps engineers
* Anyone interested in optimizing PostgreSQL performance
Contact info@mydbops.com for PostgreSQL Managed, Consulting and Remote DBA Services
Choose our Linux Web Hosting for a seamless and successful online presencerajancomputerfbd
Our Linux Web Hosting plans offer unbeatable performance, security, and scalability, ensuring your website runs smoothly and efficiently.
Visit- https://onliveserver.com/linux-web-hosting/
Recent Advancements in the NIST-JARVIS Infrastructure
Manual Testing.
1. Re: what is cyclomatic complexity? plz explain with example
Answer Cyclomatic Complexity is a White Box 0
# 1 Testing Type.
Re: what is monkey testing?
Answer Testing Software without any Test case or
# 2 formal Procedure.
N..
00000…aviating through various screens and
checking for the
Functionality with some dummy/unformatted
inputs and
Finding bugs.
Re: What is quot;Visible State Transitionquot; test? Give example
Answer Visible State Transition means first we
# 1 check state of
System and then test cases are written to
test the triggers
(Events) that causes the system transition
Re: How Severity and Priority are related to each other?
Answer Severity tells the seriousness/depth of the
# 1 bug where as
Priority tells which bug should rectify
first..
Re: I Have a login screen. Us before the release you see the screen and there
is a bug. Tell me what’s the bug. Screen: Logen : Password : | Submit |
(submit is a button)
Answer Spelling of Login...its logen on the screen
#1
Re: What type testing will be conducted at system testing? Who will conduct
each test?
Answer System testing is a type of Black box
# 3 testing. System
Testing means testing the application.
After the
Integration testing usually will do system
testing.
Functionality, Regression, and performance
testing comes
Under system testing.
2. Re: Tell me the scenario where severity Low and Priority High?
Answer Lets take an example of quot;LOGIN
# 1 APPLICATIONquot;. U r typing
Correct quot;USER IDquot; and quot;PASSWORDquot; and click
quot;OKquot; button it
Is not going to the next page so this is a
bug. This bug
Has quot;LOW SEVERITYquot; and quot;HIGH PRIORITY”. If
in the same
Example the systems crashes or hangs then
we have to
Give quot;HIGH SEVERITYquot; and quot;HIGH PRIORITYquot;.
Re: What are the test methodologies??
Answer Test methodology - the process in which
# 2 testing activity is
Determined
Example: water fall model
Re: In which situation or phase or any did u find that Manual testing is a
must instead of Automation testing
Answer If the requirements are changing
# 1 continuously manual testing
Is suitable than automation
Once the build is stable we go to
automation
Re: diff between water fall model and v-model?
Answer Waterfall model:
# 1 In this type of model the flow is
sequential starting from
The planning, design, coding and after that
testing is put
Into effect.so the testing is after the
coding only and
Not before that
V-Model:
In this model the testing starts after
business
Requirements is finished and furnished
And testing continues in parallel with the
coding
So that we can eliminate error in the
earlier stage
3. Re: What are the Techniques to be followed while writing the Test Cases?
Answer 1.Boundary value analysis (BVA) and
# 1 2.Equilance class partition (ECP)
Re: In an Text Box Expected Value is 'icici' where as actual value came up is
'icci'. Now in the Bug Report How will u rate the severity and Priority?
Answer Sevirity: low
# 1 Prority: high
Re: when the test plan will be prepared in waterfall model?
Answer After coding phase
#1
Re: What is the difference between product base company and application
company? If product base name few products, if service base name the few
services.
Answer Product based company Services
#1 based Company
1) Requirements are 1) req are
came from client
Defined by company itself
2) If req are not available
They will conduct market survey
And gather req
3) It is 4 market 3) it is 4
particular person
4) Oracle is the product 4) an
application
Re: Write 5 best test cases for : Login screen Login ( Min 5 to max 15 )
Password ( Min 5 to max 15) alphanumeric characters ans case senstive
Answer Specification- Login Screen Of Hotmail
# 1 User Id-Prajakta Password-GOD12
Test Cases:
1) Go to User Id field and without entering
data in that field
Press quot;Enterquot; key.
Expected-it should prompt message quot; Please
enter 'User ID'quot;
2) Go to login screen enter quot;User Id” and
without entering
Passwords try to click on quot;OKquot; button.
Expected-it should prompt message quot;Please
enter 'Password' quot;
4. 3) Go to login screen enter quot;User Id” and
enter wrong
Passwords try to click on quot;OKquot; button.
Expected-it should prompt message quot; Please
enter Proper
'User ID' and 'Password' quot;
4) Go to Login screen enter all required
data and press quot;OKquot;
Button then software window will open. In
that window click
On quot;Backquot; button.
Expected-It should go back to 'Login'
screen and that
Screen should not show quot;User Idquot;
and quot;Passwordquot;
5) Go to login screen enter quot;User Idquot; and
enter password as
quot;God12quot; try to click on quot;OKquot; button.
Expected-It should prompt message for
wrong Password.
Re: Write 5 best test cases for: Login screen Login (Min 5 to max 15 )
Password ( Min 5 to max 15) alphanumeric characters ans case senstive
Answer Test case ID Description Expected
#2 Actual
Severity priority
1 Enter valid username with 10
characters and with
Out enter password and click on “OK” Error
message r:
Please enter password
2 Enter password only with 6
characters and click
On “OK” Error message r: please enter
username
3 Enter username with special characters
and enter
Password with special characters and click
on “OK”
Please enter valid username and
password without
Special characters
4 Enter username with 16 characters and
enter
Password as 6 characters and click on “OK”
Please
Enter below 15 characters for username
5 Enter username as 12 characters and enter
password
5. As 3 characters and click on “OK”
Please enter min 5
Characters for password
Re: what is traceability matrix. What is traceability template
Answer Traceability matrix is nothing but mapping
# 1 between Requirements and test cases
to ensure that all requirements recovered
Re: Tell me the scenario where severity More and Priority Low?
Answer In my view there will not be that kind 0 Kris
#1 of situation since
The whole purpose of testing is to
avoid the bugs that are
Affecting the system. Therefore,
priority will be definitely
High when severity is high.
Re: Tell me the scenario where sevirity More and Priority Low?
Answer Load conditions (severity- high)
# 2 ex: does not allows load(priority-high)
ex: does not allow customer expected
load(priority-low)
Re: where do u store u'r Test cases?
Answer Test cases are normally stored in
# 1 repositories like
1.VSS - Test cases are written in excel
sheets and stored
Module by module in VSS. There will be a
separate folder
Allotted for test cases for every release.
2.Test director - In test director there is
a separate
Location PLAN TEST. Here also we can create
different
Folders and test set.
Re: if i give some thousand tests to execute in 2 days what do u do?
Answer If possible, we will automate or else,
# 1 execute only the
Test cases, which are mandatory.
Re: what is verification and validation?
6. Answer
Verification: To ensure that the s/w
# 2 correctly implements
The specific function.
Validation: To ensure that the s/w is
satisfied the Customer requirements.
Re: What is Traceability matrix? Why itis used? Can u tell me the
architecture of that?
Answer Traceability matrix is used to map between
# 1 requirements and Test cases
It is used to check all requirements are
covered or not?
Re: What is Mean by V-Module?
Answer V model is a diagram showing the map
# 3 between verification
And corresponding validation for the
application
Verification is to see that we are building
the product right
Validation is to see the the product build
is right
Re: What is meant by the bug state quot;Reproducequot;
Answer Reproduce is nothing but we need to open
# 1 again the bug
Which we found in testing with steps what
we followed to
Open the bug in previous time
Re: HOW TO WRITE THE SCENARIO FOR ATM MACHINE AND
COFFEE MACHINE? URGENT
Answer ATM machine
# 1 Checking balance
Withdraw cash
Coffee machine
Put exact change and get coffee
Put money and then cancel the transaction
Re: what is debugging and whitebox testing and what is the diff?
Answer Debugging and white box testing goes hand
# 1 in hand and
Typically done by the developers.
Debugging is done to verify that the
program runs smoothly
7. And running program shouldn't cause any
unwanted response
By the machine.
White box testing is nothing but running
the program and
Verify the actual behavior/result of the
functionality with
Expected result as predetermined.
Re: Role of Software Test Engineer in Software Company
Answer The role of a software test engineer in
# 1 company is to find
the defect. He/She should have quot;test-to-
breakquot; attitude.
He/She has to test the application taking
the customer into
mind. He should work hard for quality.
Re: Can u test a website or a webapplication manually without using any
automation tool?
Answer As per my idea we can test a webapplication
# 1 manually
without using automation but its time
consuming and might
have error so to make our task easy and
error free we use
automations tool like Qtp
Re: what is stub?Explain in testing point of view?
Answer Stub is a part of Intgeration Testing
# 5 Intergration Testing
1>Top down-Use stubs to test the module
Stub is a dummy module replaced in order to
test the main
module so that we are sure that the
integration between
both the modules works fine
2>Bottom Up-- Use driver to test the module
the test data is sent to main module thru
the drivers(also
called Test Harness)
Re: what is 4 p's? Exact difference between testing and QA
Answer Testing:
# 1 It is Prodcut level activity.
Here the primary principal is Validation.
8. It follows the procedure that is prepared
by QA.
Its principle is detecting & reporting
defects.
QA
It is Organizational activity.
Here the primary principal is Verification.
It prepares the procedure that is to be
followed by the development and Testing
team.Its principle is preventing Defects.
Re: what is Scalability,Critical Analysis
Answer Scalability is nothing but max no users
# 1 that the application can handle
Re: what is internalization?
Answer Testing related to handling foreign text
# 1 and data within
the program. This would include sorting,
importing and
exporting test and data, correct handling
of currency and
date and time formats, string parsing,
upper and lower case
handling and so forth.
Re: what is the difference between test case and test scenario.Explain with
example?
Answer Test Case is a Step which has to be
# 1 verified in order to
test a Scenario.
scenario is nothing but a series of
testcases inorder to
verify one transactional cycle.
ex:Scenario:
verifying that a user is able to manage his
e-mail inbox
such as view all messages,send a
message,manage
folders,logout..etc with a valid user login
and password
test case:
is e-mail login page is displaying
is the user able to login using his login
id and password
is he able to view his inbox
is he able to delete unwanted -mails..etc
9. quot;But interviewer expects you to give
examples related to
your previous job.quot;
Re: Diff. between STLC and SDLC?
Answer STLC-Software Test Life Cycle and SDLC is
# 1 whole Software Development Life Cycle
Re: Can any one please tell me the exact difference between the smoke
testing,sanity testing and exploratory testing?
Answer Sanity testing means initial testing done
# 2 to check the
environment well suites for the testing
process or not..
Smoke testing is similar to sanity but with
some specific
reason mentioning why our testing process
is stopped..
Exploratory testing means testing the
process without any
specific plans and schedules.
Re: What is Retesting?
Answer Executing the same test cases on the same
# 1 build but with
different inputs..
Re: Give an example for high severity and low prority bug and as well as low
severity and High prority
Answer High Severity and Low priority
#2
It is nothing but when we raise a bug
though it's severity
is high to fix that bug we need some money
definitely we
will postpone that bug
so low priority
another example for (High severity and low
pririty)
some times we get error messages system is
crashing do u
want to continue like quot;yesquot; OR quot;Noquot;
If u press YES Application should crash
if u press no application retain it's
prevoius state
10. Suppoose if we press no The application is
crashing
if we pree Yes application retaining 2 it's
previous state
It is funcntionality defect(High severity)
as far as developre is concerned he just
replaces the
funstionalities of YES and No buttons
Low priority
Re: what is mean by end to end testing?
Answer end to end testing is nothing but system
# 1 testing..testing
the application starting from scratch to
the end after
integrated all the modules.....
Re: What is the diffrence between BUILD & RELEASE ?
Answer Difference number one:Builds refer to
# 1 software that is
still in testing, release refers to
software that is
usually no longer in testing.
Re: At wht stage in the SDLC testing should be started?
Answer TESTING START FROM THE STARTING STAGE OF
# 1 SDLC THAT IS
REQUIREMENT STAGE WHERE WE PERPARE SRS OR
URS DOC.
Re: WHAT IS THE BEST WAY TO CHOOSE AUTOMATION
TOOL?(IBM)
Answer We use automation only for version wised
# 1 projects, means if
the project comes up with different
versions. Once we write
the scripts for one version, we can use
these scripts with
mulitple versions with minor changes.
So the main advantage of automation is:
1. Saves the time.
2. Saves money.
Re: Explain me about test scenarios? How will you write it?
Answer test scenario is a series of actions that
# 1 the user might
11. perform on the application or tester might
plan to do.
Ex: drawing money from ATM is a test
scenario, similarly
checking account is a scenario.
Re: what r the contents in usecase?
Answer Input actions & flow diagrams. usecase is
# 1 prepared by testlead or senior test
engineer.
Re: In what basis you will write test cases?
Answer I would Writed the Test cases Based on
# 2 Functional
Specifications and BRDs and
some more test cases using the Domain
knowledge
Re: what r the contents in defect reporting?
Answer Sl no, Bug description, Steps to reproduce,
# 1 Severity,
Priority, Bug Identifier name, Submitted
date, Build &
Assigned to.
Re: If the client identified some bugs to whom did he reported?
Answer He will report to the Project Manager.
# 1 Project Manager will
arrange a meeting with all the leads (Dev.
Manager, Test
Lead and Requirement Manager) then raise a
Change Request
and then, identify which are all the
screens going to be
impacted by the bug. They will take the
code and correct it
and send it to the Testing Team.
Re: what is TRM?
Answer TRM is nothing but Test Responsibility
# 1 matrix.
It is the matrix mapped between Development
stages and Test factors.
Re: How many Test Managers in Test Director? Skjha2000@rediffmail.com
Answer 4
# 1 requirements manager
test plan manager
test lab manager
defects tracking manager
12. for more details refer test director user
guide
Re: Main Diffrences between Test Director and Bugzilla?
Answer Test Director is Test Management Tool
# 1 includes(Test Plan,
Running Tests and Reporting Bugs) whereas
Bugzilla is Bug Reporting tool only.
Re: How to fetch data from excel sheet using TEST DIRECTOR
Answer there is an option in Test director advance
# 1 version 8.0 in
that in file menu there is import file
option
click on that and give the path where it is
the path click
on ok
Re: How many scripts u use to run daily?
Answer On an Average we Write n Execute only 1 or
# 1 2 Automation
Scripts each day. (Depends on the
complexity of an
Aplication).
We write n execute 20 to 25 test cases
manually...ie manual
Testing.
Re: What is driver in testing point of view?
Answer Test Driver or Test Harness: A program or
# 1 test tool used to
Execute tests. Also known as a Test
Harness.
Re: What is the diff between IE and Netscape in a web testing on a login
page.
Answer Netscape does not support HTML code
# 2 IE Can Support
Re: what r the GUI Test Cases for calculator?
Answer 1.check for all the buttons are available r
# 1 not
2.check the screen for displaying
3.check consistency of all the buttons
3.check the spelling for the objects
13. Re: what is Application state, Base state and call state?
Answer Application state: When we do any action in
# 1 the application,
the changed state is called as Application
state.
Base State: The initial state of the
application just after
evoked/opened.
Call State: Before performing any action on
the application,
the state of the application what we are
visualising that it
will happen after doing a certain step of
actions.
Re: In which stage more defects found means anlaysis,design,coding,testing
and maintance?
Answer In Testing stage. why b'coz while we
# 1 testing the product
more defects will be raised by test
engineers in Testing
stage only.
Re: what r the GUI Test Cases for calculator?
Answer 1.check for all the buttons are available r
# 1 not
2.check the screen for displaying
3.check consistency of all the buttons
3.check the spelling for the objects
Re: what is the difference between use case and test case?
Answer use case contains USER actions and System
# 1 response
Test case contains only user actions we
dont know system response.
Re: What is Impact analysis. How to do impact analysis in yr project..
Answer impact analysis means when we r doing
# 1 regressing testing at
that time we r checking that the bug fixes
r working
Properly, and by fixing these bug other
components are
working as per their requirements r they
got disturbed.
14. Re: how will u know whether ur reported bug is accepted r rejected?
Answer if the defect is rejected then dev team
# 1 will give us
intimate with the proper reasons through e
mail or bug
tracking tool if it is accepted then dev
team ask 4 screen shots
Re: What are the contents in quot;Requirements Traceability Matrixquot; not in quot;
Test Responsibility Matrixquot;?
Answer Contents of Requirements Traceability
# 1 Matrix / RTM :
Release Name
Test Case Name
High level design
Low Level Design
Test Case Execution
Automation Execution
What is the cost of quality?
Answer You can say that cost of quality is the
# 1 combination of
Prevention Cost + Appraisal Cost + Failure
Cost
Re: What is quot;Visible State Transitionquot; test? Give example
Answer Visible State Transition means first we
# 1 check state of
system and then test cases are written to
test the triggers
(events) that causes the system tarnsition
Re: What is Test Scripts What is static testing and dyanmic testing. Explain
with an example
Answer Test Scripts: is used to test a particular
# 1 functionality
(business rule). It may consist of 1 or
more Test Cases.
static testing: Testing of an object
without execution on a
computer. (eg. review
document,inspection,walk thro')
simply said static means verification.
dynamic testing: The process of evaluating
15. a system or
component based upon its behaviour during
execution
(eg. functional testing, regression
testing, UAT etc.,)
means validation
What is 'configuration management'?
Configuration management covers the processes used to contro coordinate, and track:
l,
code, requirements, documentation, problems, change requests, designs,
tools/compilers/libraries/patches, changes made to them, and who makes the changes.
How is testing affected by object-oriented designs?
Well-engineered object-oriented design can make it easier to trace from code to internal
design to functional design to requirements. While there will be little affect on black box
testing (where an understanding of the internal design of the applicat on is unnecessary),
i
white-box testing can be oriented to the application's objects. If the application was well-
designed this can simplify test design.
Re: Is automated testing better than manual testing. If so, why
Answer Automated testing and manual testing have
# 1 advantages as Well as disadvantages
Advantages:
It increases the efficiency of testing
process
Speed in process
Reliable
Flexible
Disadvantages
Tools should have compatibility with our
developement or
deployment
tools needs lot of time initially
If the requirements are changing
continuously Automation is
Not suitable
Manual: If the requirements are changing
continuously
Manual is suitable
Once the build is stable with manual
testing then only we
go 4 automation
Disdavantages:
It needs lot of time
16. We can not do some type of testing manually
E.g Performanence
Re: If you have an application to test and there are no requirement specs, no
test cases, no documents, you don’t know even the functionality then how
would you perform testing?
Answer Simply says Ad hoc testing. Without knowing
# 1 the
Functionality, without following any
sequence,---doing the
Testing called Ad hoc testing.
Re: In an Testing interview the following question asked. Who will write use
cases?
Answer Use Cases are prepared by the Business
# 2 Development Team only
Re: Will you write a test plan in all phases?
Answer No., testplan will be written only once and
# 2 ideally needs
to be updates with every change in the
project!
Re: what r the contents in use case?
Answer Input actions & flow diagrams
#1
Re: what r the contents in defect reporting?
Answer Sl no, Bug description, Steps to reproduce,
# 1 Severity,
Priority, Bug Identifier name, Submitted
date, Build &
Assigned to.
Re: what is the goal of system testing?
This is the last stage of testing at offshore, which covers both
Functional and non-functional testing.
Re: In what basis you will write test cases?
Answer I would Write the Test cases Based on
# 2 Functional
Specifications and BRDs and
17. Some more test cases using the Domain
knowledge.
Re: Overall what percentage of positive and negative test cases would you
write?
Answer That depends on the screen. Most of the
# 1 times, I will
verify for the -ve test conditions.
Re: what is thee diff between functionality testing and blockbox testing?
Answer Functional Testing is the major part of
# 2 Black box testing
in which the functionality of the AUT
should be tested.
Where as Black Box Testing means testing
the application
based on its performance with out
concerning its internal
design.
Re: What is Test Server?
Answer test Server is nothing but the place where
# 1 the developers
put their development modules, which are
accessed by the
testers to test the functionality
(SoftBase).
Re: what is test log? tell the process?
Answer A test log is nothing but, what are the
# 1 test cases we r
executed, in what order we executed, who
executed that test
cases and what is the status of the test
case(pass/fail).
Re: Did you write test cases of design phase?
Answer Yes We can write test cases at the design
# 1 phase
At the time of designing we should be ready
with test cases
Re: What are the main key components in Web applications and client and
18. Server applications? (differences)
Answer For Web Applications: Web application can
# 1 be implemented
using any kind of technology like Java,
.NET, VB, ASP, CGI&
PERL. Based on the technology,We can derive
the components.
Let's take Java Web Application. It can be
implemented in
3 tier architecture. Presentation tier
(jsp, html, dthml,
servlets, struts). Busienss Tier (Java
Beans, EJB, JMS)
Data Tier(Databases like Oracle, SQL Server
etc., )
If you take .NET Application, Presentation
(ASP, HTML,
DHTML), Business Tier(DLL) & Data Tier
( Database like
Oracle, SQL Server etc.,)
Client Server Applications: It will have
only 2 tiers.
One is Presentation (Java, Swing) and Data
Tier (Oracle,
SQL Server). If it is client Server
architecture, The
entire application has to be installed on
the client
machine. When ever you do any changes in
your code, Again,
It has to be installed on all the client
machines. Where
as in Web Applications, Core Application
will reside on the
server and client can be thin
Client(broswer). Whatever the
changes you do, You have to install the
application in the
server. NO need to worry about the
clients.Because, You
will not install any thing on the client
machine.
Re: Does functional testing comes under Black box or white box testing?
Answer Functional Testing comes under Black Box
# 2 testing. Because
tester does not know about the internal
details of the
program. Based up on the test cases he will
test.
19. Re: At what phase tester role starts?
It is based on SDLC if it is v-model testers work starts after receiving FRS and if it is
waterfall model testers work will be after coding phase.
Re: Explain me about test scenarios? How will you write it?
Answer test scenario is a series of actions that
# 1 the user might
perform on the application or tester might
plan to do.
Ex: drawing money from ATM is a test
scenario, similarly
checking account is a scenario.
Re: If the client identified some bugs to whom did he report?
Answer He will report to the Project Manager.
# 1 Project Manager will
arrange a meeting with all the leads (Dev.
Manager, Test
Lead and Requirement Manager) then raise a
Change Request
and then, identify which are all the
screens going to be
impacted by the bug. They will take the
code and correct it
and send it to the Testing Team.
Re: Explain ETVX concept?
Answer E- Entry Criteria
# 1 T- Task
V- Validation
X- Exit Criteria
ENTRY CRITERIA:
Input with 'condition' attached.
e.g. Approved SRS document is the entry
criteria for the
design phase
TASK:
Procedures.
e.g. Preparation of HLD,LLD etc.
VALIDATION:
Building quality & Verification activities
e.g. Technical reviews
EXIT CRITERIA:
Output with 'condition' attached.
e.g. Approved design document
20. It is important to follow ETVX concept for
all phases in
SDLC.
Re: What do u do if the bug that u found is not accepted by the developer and
he is saying its not reproducable. Note: The developer is in the onsite location
Answer Sometimes bug is not reproducible it is
# 2 becoz of different
environment
suppose dev team using other environment
and u r using
different environment
at this situation there is chance of bug
not reproducing.
at this situtation plz check the
environment in the base
lione documents that is functional
documents
if the environment which we r using is
correct
we will raise it as defect
We will take screen shots and sends them
with test
procedure also
Re: What is the diff between Functional and regression testing and do u
execute same test case or write new one for regression
Answer During functional Testing if we found any
# 1 defect we report
bug to dev team b they will fix and resolve
the bug and
modified build to us
We will execute some of that test cases or
total test cases
Which we executed previously
while in funnctional testing we will do
many more not only
regression buy also retesting n some other
Re: How many scripts u use to run daily?
Answer On an Average we Write n Execute only 1 or
# 1 2 Automation
Scripts each day.(depends on the complexity
of an
aplication).
21. We write n execute 20 to 25 test cases
manually...ie manual
testing.
Re: How did u perform regression testing what r the steps involved?
Answer First of all sir, U must know whats
# 1 Regression Testing is
(RT): It is the testing done on a module
when its modified.
Some times RT is done using Automation
Tools.
RT is of 3 kinds :
Unit : Testing is done only on that part
where the module
is modified.
Regional : Testing is done on those parts
inan application
whereever the changes made in the module
gets affected.the
modified modeule is also tested.
Full: the whole application is tested.
Re: What is the diff between IE and netscape in a web testing on a login page.
Answer Netscape doesn’t recognize ENTER key
#1
Re: What is White Box testing and who is responsible for white box testing?
Answer Testing the application with the knowledge
# 1 of the internal
Structure..it comes under white box
testing..In General
Developers are responsible for white box
testing?
Re: What are the Techniques to be followed while writing the Test Cases?
Answer 1.Boundary value analysis(BVA)and
# 1 2.Equilance class partition(ECP)
Re: what is change management and change request
Answer change request is nothing but either it is
# 1 a missed defect
or enhancement request 4 future expansion
22. it is recieved in Maintanace phase
Change management is nothing but when a
change is
Performed comparing the changes and in
which change we got
defect
Re: how u can do integration testing and what r the approaches u need to
follow?
Answer The integration Testing is doing for
# 1 integrated modules. So
first of all we required an integrated
application to do
the integration testing.
Here we have to check wether the integrated
modules are
working properly or not. This can be do
through the
integration test cases.
For example Creating a user account and
login to the system
are two modules.
Here u can see the Create User is a module
and Login user
Is another module. So First we create a
user then with the
new username and password we logon to the
system. If it is
working as per the expectation then the
test is pass.
Is it Clear?
Re: what type of review process u r following in u'r company?
Answer I think there are three types of review
# 2 process followed in
a company
1. SRS based review
2. BRS based review
3. TRM based review
Re: what is exact meaning of SNAP SHOT.how and when it will be taken
Answer In the field of testing. Snap shot is the
# 2 picturezation of
the error in your screen. When ever you
write and test case
and excute it.You may same defect or a
23. message pops up on
the screen.During that time just press the
print screen key
in your key board and then save it as a
bitmap image. Then
when you report a defect in a TOOL just
attach the file so
that the developer can get some idea of the
image which you
picturize in your computer screen when you
are exiquting
the test case.
Re: What is Six sigma ?Expain.
Answer Six Sigma means a measure of quality that
# 1 strives for near
perfection.
Six Sigma is a disciplined, data-driven
approach and
methodology for eliminating defects
(driving towards six
standard deviations between the mean and
the nearest
specification limit) in any process -- from
manufacturing
to transactional and from product to
service.
Re: what is the difference between test case and test scenario.Explain with
example?
Answer Test Case is a Step which has to be
# 1 verified in order to
test a Scenario.
scenario is nothing but a series of
testcases inorder to
verify one transactional cycle.
ex:Scenario:
verifying that a user is able to manage his
e-mail inbox
such as view all messages,send a
message,manage
folders,logout..etc with a valid user login
and password
test case:
is e-mail login page is displaying
is the user able to login using his login
id and password
is he able to view his inbox
is he able to delete unwanted -mails..etc
quot;But interviewer expects you to give