The document discusses QA automation, including challenges like ensuring tests are resilient, simple, and comprehensive. It also discusses solutions like developing an automation framework to write high-level tests and using infrastructure for speed and parallelization. The document recommends considering outsourcing automation by evaluating factors like criticality, expertise needs, and test integration.
Grokking Techtalk: Problem solving for sw engineers
Introduction to problem solving skill for software engineering. Including:
- Problem definition
- Ladder of abstraction
- Causal Analysis
- Trade-off Analysis
- Separation Principles
This document discusses source code version control features in Microsoft Visual Studio 2010 and Team Foundation Server, including changesets, check-in policies, workspaces, shelving, labeling, branching and merging. It also covers how version control integrates with other TFS components like work item tracking and test-driven development. The presentation emphasizes how TFS provides full traceability, visibility and reporting across the entire application lifecycle.
The document summarizes a presentation about using Microsoft Visual Studio 2010 and Team Foundation Server. It discusses using these tools to trace requirements, code check-ins, builds, and test results. It also provides an overview of Team Foundation Server, describing its main functions like version control, work item tracking, and build automation.
This document describes using unit testing and dependency injection to test modules in isolation. It notes that unit tests can be written as code so they are not forgotten or lost like manual test cases. However, modules may depend on other objects like databases or APIs. To address this, the document recommends using interfaces and dependency injection and mocking dependencies with fake objects so the primary module can be tested without external dependencies. This allows each module to be tested in isolation and for unit tests to serve as technical specifications that can be reused across platforms.
The document provides an overview of software testing techniques, focusing on black-box testing. It discusses the basics of software testing, including verification and validation practices. It also describes the two main techniques of black-box and white-box testing, as well as six types of testing involving both: unit testing, integration testing, functional testing, system testing, stress testing, and performance testing. Finally, it discusses strategies for writing efficient test cases that can find faults with minimal effort.
This document provides an overview of software testing techniques, including black-box and white-box testing. It discusses the basics of software testing throughout the development lifecycle, including verification to check that the product is being built correctly and validation to ensure the right product is being built. Six types of testing involve both black-box and white-box approaches. The document also describes strategies for writing fewer test cases while still finding faults, and using templates for defined, repeatable test cases.
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.
Tutorial of web application load testing in selinium
Selinium IDE is a specialized tool for performing functional testing on web applications. It allows users to record test cases consisting of steps like entering URLs, filling forms, and verifying results. These test cases can then be run automatically by Selinium IDE to ensure web applications work as expected. The document provides details on downloading, installing, and using Selinium IDE to create and run test cases for a sample web application.
This document discusses various techniques for maintaining code quality, including pair programming, test-driven development, code reviews, and self-documenting code. It notes that pair programming involves two developers sharing one monitor, keyboard, and mouse to collaboratively write code. Benefits include higher quality code, knowledge sharing, and a teaching tool. Code reviews search for bugs, design flaws, nonconformance with requirements or style guides. Comments should explain why code is written a certain way rather than describing how.
The document introduces aspect-oriented programming (AOP) as a programming methodology that aims to modularize code into distinct processes or concerns. It discusses how AOP can help address issues with traditional object-oriented programming (OOP), such as duplicate code from cross-cutting concerns that span multiple classes. The key idea of AOP is to define aspects separately from the core program and then weave them together using an aspect weaver. This allows cross-cutting concerns to be modularized independently from the core program logic.
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.
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 discusses several software design patterns that are useful for Android development including:
- Renderer pattern: Decouples rendering process from adapters by separating complex object instantiation from representation using Builder pattern and delegating rendering tasks.
- Repository pattern: Abstracts the data source/origin in a system to decouple client code from implementation details like memory storage, databases, or external APIs.
- Other patterns discussed include Adapter, Memento, Chain of Responsibility, and Model-View-Controller. The document provides examples of how these patterns can solve problems like rendering different video types or saving Android activity state.
Acceptance criteria define specific, measurable conditions that must be met for a user story or feature to be accepted. They help ensure stakeholders have a shared understanding of what needs to be delivered before development begins. Good acceptance criteria are independent of implementation, written from the user perspective, and use a format like Given, When, Then. They describe what is expected rather than how it will be implemented. Acceptance criteria should be defined before development starts to guide testing and determine when a user story is complete.
This is where scriptless test automation comes into the picture. Businesses today may utilize Scriptless Test Automation to automate test cases without having to worry about the complexities of coding. It speeds up the time to learn and build code, resulting in a shorter time to market, a greater return on investment, and increased coverage with little maintenance.
No code testing revolutionizes web and mobile app testing by enabling business users and non-technical personnel to automate tests without writing test scripts.
This document introduces Adam Tuliper and Christopher Harrison from Microsoft and provides an overview of their session on implementing Entity Framework with MVC. The session will cover introducing Entity Framework, beginning code first development, managing relationships and transactions, and integrating additional features. Attendees will learn how to use Entity Framework to access and manage data in an MVC application.
Good quality code is an essential property of a software because it could lead to financial losses or waste of time needed for further maintenance, modification or adjustments if code quality is not good enough.
SOLID is a mnemonic device for 5 design principles of object-oriented
programs (OOP) that result in readable, adaptable, and scalable code.
S - Single Responsibility Principle.
O - Open Closed Principle.
L - Liskov Substitution Principle.
I - Interface Segregation Principle.
D - Dependency Inversion Principle.
Grokking Techtalk: Problem solving for sw engineers9diov
Introduction to problem solving skill for software engineering. Including:
- Problem definition
- Ladder of abstraction
- Causal Analysis
- Trade-off Analysis
- Separation Principles
This document discusses source code version control features in Microsoft Visual Studio 2010 and Team Foundation Server, including changesets, check-in policies, workspaces, shelving, labeling, branching and merging. It also covers how version control integrates with other TFS components like work item tracking and test-driven development. The presentation emphasizes how TFS provides full traceability, visibility and reporting across the entire application lifecycle.
The document summarizes a presentation about using Microsoft Visual Studio 2010 and Team Foundation Server. It discusses using these tools to trace requirements, code check-ins, builds, and test results. It also provides an overview of Team Foundation Server, describing its main functions like version control, work item tracking, and build automation.
This document describes using unit testing and dependency injection to test modules in isolation. It notes that unit tests can be written as code so they are not forgotten or lost like manual test cases. However, modules may depend on other objects like databases or APIs. To address this, the document recommends using interfaces and dependency injection and mocking dependencies with fake objects so the primary module can be tested without external dependencies. This allows each module to be tested in isolation and for unit tests to serve as technical specifications that can be reused across platforms.
The document provides an overview of software testing techniques, focusing on black-box testing. It discusses the basics of software testing, including verification and validation practices. It also describes the two main techniques of black-box and white-box testing, as well as six types of testing involving both: unit testing, integration testing, functional testing, system testing, stress testing, and performance testing. Finally, it discusses strategies for writing efficient test cases that can find faults with minimal effort.
This document provides an overview of software testing techniques, including black-box and white-box testing. It discusses the basics of software testing throughout the development lifecycle, including verification to check that the product is being built correctly and validation to ensure the right product is being built. Six types of testing involve both black-box and white-box approaches. The document also describes strategies for writing fewer test cases while still finding faults, and using templates for defined, repeatable test cases.
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.
Tutorial of web application load testing in seliniumKevalkumar Shah
Selinium IDE is a specialized tool for performing functional testing on web applications. It allows users to record test cases consisting of steps like entering URLs, filling forms, and verifying results. These test cases can then be run automatically by Selinium IDE to ensure web applications work as expected. The document provides details on downloading, installing, and using Selinium IDE to create and run test cases for a sample web application.
This document discusses various techniques for maintaining code quality, including pair programming, test-driven development, code reviews, and self-documenting code. It notes that pair programming involves two developers sharing one monitor, keyboard, and mouse to collaboratively write code. Benefits include higher quality code, knowledge sharing, and a teaching tool. Code reviews search for bugs, design flaws, nonconformance with requirements or style guides. Comments should explain why code is written a certain way rather than describing how.
The document introduces aspect-oriented programming (AOP) as a programming methodology that aims to modularize code into distinct processes or concerns. It discusses how AOP can help address issues with traditional object-oriented programming (OOP), such as duplicate code from cross-cutting concerns that span multiple classes. The key idea of AOP is to define aspects separately from the core program and then weave them together using an aspect weaver. This allows cross-cutting concerns to be modularized independently from the core program logic.
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.
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 discusses several software design patterns that are useful for Android development including:
- Renderer pattern: Decouples rendering process from adapters by separating complex object instantiation from representation using Builder pattern and delegating rendering tasks.
- Repository pattern: Abstracts the data source/origin in a system to decouple client code from implementation details like memory storage, databases, or external APIs.
- Other patterns discussed include Adapter, Memento, Chain of Responsibility, and Model-View-Controller. The document provides examples of how these patterns can solve problems like rendering different video types or saving Android activity state.
Acceptance criteria define specific, measurable conditions that must be met for a user story or feature to be accepted. They help ensure stakeholders have a shared understanding of what needs to be delivered before development begins. Good acceptance criteria are independent of implementation, written from the user perspective, and use a format like Given, When, Then. They describe what is expected rather than how it will be implemented. Acceptance criteria should be defined before development starts to guide testing and determine when a user story is complete.
Improving ROI with Scriptless Test AutomationMindfire LLC
This is where scriptless test automation comes into the picture. Businesses today may utilize Scriptless Test Automation to automate test cases without having to worry about the complexities of coding. It speeds up the time to learn and build code, resulting in a shorter time to market, a greater return on investment, and increased coverage with little maintenance.
No code testing revolutionizes web and mobile app testing by enabling business users and non-technical personnel to automate tests without writing test scripts.
Lightning Talks by Globant - Automation (This app runs by itself ) Globant
When you add new features to your application a lot of things can happen. Do you believe that the app is able to test itself by using automation? Just imagine testing everything manually due to that change. Do you know how many people will be needed to complete this process? The power of automated testing in the development lifecycle allows us things such as scheduling, and executing tests at any time with a big scope on thousands of mobile devices, websites and multiple browsers simultaneously making sure everything is working as expected.
Automation testing involves using software tools to execute pre-scripted tests on an application before its release. It aims to simplify and automate as much testing effort as possible. Automation testing tools can execute tests, report outcomes, and compare results across test runs. Manual testing of multilingual sites is time-consuming and prone to errors, while automation testing can run unattended and is faster. Risky, time-consuming, repetitive, and difficult tests are best candidates for automation. Test tool selection depends on the application's technology. The scope of automation should be defined and include important, reused, and complex features. Automation brings benefits like repeatability, reusability, reliability, speed, comprehensiveness, and cost
This document discusses best practices for developing an automated testing framework. It recommends using a hybrid keyword-driven and data-driven approach to reduce scripting efforts. Some key points covered include the benefits of automation like reduced costs and increased speed/accuracy over manual testing. It also discusses factors to consider when selecting an automation tool, common challenges, and provides an example case study showing the ROI achieved through automation. Best practices emphasized include loose coupling of framework components, reuse of generic libraries, and treating framework development as a distinct project.
What is scriptless test automation and what are its benefits.pdfpcloudy2
In today’s fast-evolving technological landscape, the realm of test automation has seen significant advancements, not just in quantity but also in quality.
A Comparative Guide to Automation and Manual Testing.pdfkalichargn70th171
Consumers want their applications to work perfectly each time. If your app is rife with performance issues, bugs, and glitches, it can lose its user base in no time due to its flawed quality. As a result, testing your software product is imperative to ensure project teams check, verify, and validate the functionality of the developed software and deliver optimal user experiences.
This document provides an introduction to automation testing. It discusses the need for automation testing to improve speed, reliability and test coverage. The document outlines when tests should be automated such as for regression testing or data-driven testing. It also discusses automation tool options and the process for automating tests. While automation testing provides benefits like time savings, it also has limitations such as the need for programming skills and maintenance of test code. Key challenges of automation testing include unrealistic expectations of tools and dependency on third party integrations.
This document provides an introduction to automation testing. It discusses the need for automation testing to improve speed, reliability and test coverage. The document outlines when tests should be automated such as for regression testing or data-driven testing. It also discusses automation tool options and the types of tests that can be automated, including functional and non-functional tests. Finally, it addresses the advantages of automation including time savings and repeatability, as well as challenges such as maintenance efforts and tool limitations.
Testing is a major part of the Application Development Life Cycle (ADLC). It helps in eliminating the defects and issues early from the product and helps in delivering quality products to the end users.
Automated software testing is critical to success in today’s competitive business climate. As test automation specialists, TestingXperts, offers a comprehensive range of test automation services to meet your goal of increasing velocity throughout the software development lifecycle.
An Ultimate Guide to Continuous Testing in Agile Projects.pdfKMSSolutionsMarketin
As more businesses apply Continuous Integration and Continuous Delivery (CI/CD) to release their software faster, Continuous testing becomes the final piece that completes a continuous development process. By automatically testing code right after developers submit it to the repository, testers can locate bugs before another line of code is written.
Software Test Automation - A Comprehensive Guide on Automated Testing.pdfkalichargn70th171
Moving to a more digitally focused era, the importance of software is rapidly increasing. Software tools are crucial for upgrading life standards, enhancing business prospects, and making a smart world. The smooth and fail-proof functioning of the software is very critical, as a large number of people are dependent on them.
Automation testing involves developing and executing tests that can run unattended, comparing actual and expected results. The major objectives of automation testing are to speed up testing, reduce costs and time, and increase quality. Automation testing is faster than manual testing and can test more scenarios. However, high upfront investment is required for tools and training. Both manual and automation testing are needed as automation does not cover all test cases. Popular automation testing tools include Selenium, QTP, and TestComplete.
Mindtree’s upstream testing enables effective and early testing, constantly increasing the coverage during the development phase. It empowers developers to boost their productivity and allows the QA team to focus on integration and system testing.
The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Similar to Getting Started With QA Automation (20)
Lots of bloggers are using Google AdSense now. It’s getting really popular. With AdSense, bloggers can make money by showing ads on their websites. Read this important article written by the experienced designers of the best website designing company in Delhi –
React Native vs Flutter - SSTech SystemSSTech System
Your project needs and long-term objectives will ultimately choose which of React Native and Flutter to use. For applications using JavaScript and current web technologies in particular, React Native is a mature and trustworthy choice. For projects that value performance and customizability across many platforms, Flutter, on the other hand, provides outstanding performance and a unified UI development experience.
introduction of Ansys software and basic and advance knowledge of modelling s...sachin chaurasia
Ansys Mechanical enables you to solve complex structural engineering problems and make better, faster design decisions. With the finite element analysis (FEA) solvers available in the suite, you can customize and automate solutions for your structural mechanics problems and parameterize them to analyze multiple design scenarios. Ansys Mechanical is a dynamic tool that has a complete range of analysis tools.
CViewSurvey Digitech Pvt Ltd that works on a proven C.A.A.G. model.bhatinidhi2001
CViewSurvey is a SaaS-based Web & Mobile application that provides digital transformation to traditional paper surveys and feedback for customer & employee experience, field & market research that helps you evaluate your customer's as well as employee's loyalty.
With our unique C.A.A.G. Collect, Analysis, Act & Grow approach; business & industry’s can create customized surveys on web, publish on app to collect unlimited response & review AI backed real-time data analytics on mobile & tablets anytime, anywhere. Data collected when offline is securely stored in the device, which syncs to the cloud server when connected to any network.
A Comparative Analysis of Functional and Non-Functional Testing.pdfkalichargn70th171
A robust software testing strategy encompassing functional and non-functional testing is fundamental for development teams. These twin pillars are essential for ensuring the success of your applications. But why are they so critical?
Functional testing rigorously examines the application's processes against predefined requirements, ensuring they align seamlessly. Conversely, non-functional testing evaluates performance and reliability under load, enhancing the end-user experience.
In this talk, we will explore strategies to optimize the success rate of storing and retaining new information. We will discuss scientifically proven ideal learning intervals and content structures. Additionally, we will examine how to create an environment that improves our focus while you remain in the “flow”. Lastly we will also address the influence of AI on learning capabilities.
In the dynamic field of software development, this knowledge will empower you to accelerate your learning curve and support others in their learning journeys.
Responsibilities of Fleet Managers and How TrackoBit Can Assist.pdfTrackobit
What do fleet managers do? What are their duties, responsibilities, and challenges? And what makes a fleet manager effective and successful? This blog answers all these questions.
Seamless PostgreSQL to Snowflake Data Transfer in 8 Simple StepsEstuary Flow
Unlock the full potential of your data by effortlessly migrating from PostgreSQL to Snowflake, the leading cloud data warehouse. This comprehensive guide presents an easy-to-follow 8-step process using Estuary Flow, an open-source data operations platform designed to simplify data pipelines.
Discover how to seamlessly transfer your PostgreSQL data to Snowflake, leveraging Estuary Flow's intuitive interface and powerful real-time replication capabilities. Harness the power of both platforms to create a robust data ecosystem that drives business intelligence, analytics, and data-driven decision-making.
Key Takeaways:
1. Effortless Migration: Learn how to migrate your PostgreSQL data to Snowflake in 8 simple steps, even with limited technical expertise.
2. Real-Time Insights: Achieve near-instantaneous data syncing for up-to-the-minute analytics and reporting.
3. Cost-Effective Solution: Lower your total cost of ownership (TCO) with Estuary Flow's efficient and scalable architecture.
4. Seamless Integration: Combine the strengths of PostgreSQL's transactional power with Snowflake's cloud-native scalability and data warehousing features.
Don't miss out on this opportunity to unlock the full potential of your data. Read & Download this comprehensive guide now and embark on a seamless data journey from PostgreSQL to Snowflake with Estuary Flow!
Try it Free: https://dashboard.estuary.dev/register
Are you wondering how to migrate to the Cloud? At the ITB session, we addressed the challenge of managing multiple ColdFusion licenses and AWS EC2 instances. Discover how you can consolidate with just one EC2 instance capable of running over 50 apps using CommandBox ColdFusion. This solution supports both ColdFusion flavors and includes cb-websites, a GoLang binary for managing CommandBox websites.
Sami provided a beginner-friendly introduction to Amazon Web Services (AWS), covering essential terms, products, and services for cloud deployment. Participants explored AWS' latest Gen AI offerings, making it accessible for those starting their cloud journey or integrating AI into coding practices.
4. Testing My New Car
Which way is
the best way
to test my new car?
1
2
3
GUNG HO!
5. Repetition Is Hell
Regression testing is the process of
testing changes to computer programs
to make sure that the older
programming still works with the new
changes.
Tests need to be repeated for every
change or bug fix, in different
environments and with different
configurations and data sets.
Manual regression tests
are not realistically
possible for enterprise
applications!
6. Automation Benefits
Regression tests become feasible (Safety Net)
Quality Assurance Team can focus on testing new features and
non automatable aspects of testing (e.g. UX)
Failed tests can be sent to developers and replayed
Written QA tests are a repository of knowledge that stays in the
organization and survives turnovers
8. The Test Driver
…
In QA Automation, a Driver is a tool that
can control and ‘drive’ the user interface
of an application on a specific client.
Drivers can programmatically open or
close applications, simulate mouse and
keyboard interactions, and much more!
TEST DRIVER INTERFACE
DRIVER 1
Client 2 Client NClient 1
DRIVER 2 DRIVER N…
Example: Selenium WebDriver
9. Driver Responsibilities
Open/close applications
Select UI elements (By Id, Name, XPath, etc.)
Simulate mouse, keyboard or gesture interactions
Time control (waits)
Assertions
Remote execution
Screenshots, e-mails, etc.
Comply with common interfaces
10. The Recorder
In QA Automation, a Recorder is a tool
that can automatically record all the
actions manually performed by a user
(QA Analyst) and convert them into
commands for the driver and save them
as an independent test.
Recorders can also replay the
commands on schedule or on demand,
as well as export the test(s) in different
formats.
11. Programmable API
Drivers can also be instructed using
common programming languages.
Using a programming language to write
tests will provide fine-grained control
upon the driver, as well as the ability to
share common commands between tests.
Using directly the API this will increase
the complexity of tests, making them
obscure to non-developers.
14. Resilience
Resilient QA Tests are loosely dependent from:
Time
Application speed (unless it is a performance test)
Screen structure and position of elements
Data/Content
Culture
Each other!
The ability to recover from or adjust
easily to misfortune or change
15. Simplicity
Simple QA Tests can be:
Written by QA analysts with minimal training
Clearly understood by any domain expert
Easily maintained as requirements change
Composed from simple and powerful building blocks
The quality of being easy to understand or use
16. Comprehensiveness
Comprehensive QA Tests run on:
Multiple operating systems
Multiple clients (e. g., browsers)
Multiple hardware devices
Multiple configuration scenarios
Different Data Sets
Covering completely or broadly
17. Need For Speed
If we have 1000 tests
To run on 3 platforms/browsers
Average UI test duration: 3 minutes
(1000 x 3 x 3) /60 /24 = Over 6 days!
We need tests to run in parallel!!
19. Automation Framework
Development
Team
QA Team
Automation Framework
Test Driver
High Level QA Tests
An automation framework is a software
produced by the development team that allows
QA Analysts to express tests at a higher level,
utilizing reusable building blocks, hiding
unnecessary complexity and technical details.
20. Automation Framework
1. Open Login Page
2. Type “giovanni” in textbox with id = “tbxUserName”
3. Type “secretpassword” in textbox with id = “tbxPassword”
4. Click on button with Id “btnSignIn”
5. Wait for home page title
Login “giovanni” “secretpassword”
Without Automation Framework
With Automation Framework
21. Infrastructure
Virtual Machines Containers Cloud
In House Infrastructure Testing as a Service
Do you have available servers?
Does your automation suite support remote drivers?
…and many more…
22. Outsourcing Automation?
Should you pay a third party company to write your QA tests?
You may want to consider the following questions:
How critical is QA Testing to the success of your business?
What kind of domain expertise is required to test your applications?
What would be the impact of turnover in your testing process?
How will write test cases and verify that have been correctly
automated?
How will ensure that your test suite will be easily maintainable over
time?
How are Development and QA tests going to be integrated?
23. Share! Don’t be a stranger!
Share you team knowledge with other AFS teams :
• What are your testing best practices?
• Tell us your successful automation experiences
• What have learned from past failures?
