The document discusses agile testing and how it differs from traditional testing methodologies. It outlines how agile transformations affect testing practices, requiring testers to shift from solely writing test scripts to participating in requirements definition and writing test cases earlier. It also discusses common types of agile testing like exploratory and risk-based testing. The document provides examples of open source tools that can be used for agile testing and highlights both advantages like reduced costs and faster delivery, and disadvantages like less documentation.

1. AGILE TESTING
AT does not stand for Arzu TARIMCI
stands for Agile Testing

2. Does Agile
transformation affect
testing methodologies?
Types of
Agile Testing
Open source tools
for agile testing
@Bansky

3. Common steps of SDLC
Requirements
Requirement
Planning
Design
Analyze and
Coding
Test
Demonstrating
design
corresponds to
requirements
Release
Deployment
Post Actions
Software
maintenance
Test: La part before release

4. Agile
Requirements
Design
Test
Release
Post Actions
Requirements
Design
Test
Release
Post Actions
Requirements
Design
Test
Release
Post Actions
Requirements
Design
Test
Release
Post Actions
1. iteration 2. iteration 3. iteration n. iteration

5. Does Agile transformation affect testing
methodologies?
❑ Culture Changes
❑ The Product Owners and Developers also played a big part in achieving agile testing.(SUMRELL)
❑ Developers started to update test requirements
❑ Developer unit testing was started and %40 percent less time: QA engineers have been spending
❑ The skill set for our QA Engineers would need to shift. They were all writing test scripts to test sophisticated data validation and workflows
❑ Quality could no longer be solely owned by the QA team. The entire participate in the definition of acceptance and they write
test cases prior to the sprint even beginning.
❑ Pair testing, risk based testing and exploratory testing were accepted some of the key practices to achieve the goal of quality control(KAUR).
❑ Changes on time management
❑ Weekly meetings should be held to establish frequent and direct communication
with project stakeholders. Agile testing is that which involves testing from the customer' s side as early stage.
Early stage testing is also called unit testing.
❑ Test & Use Cases
❑ The adoption of conceptual models of Use Cases
❑ The detailing of Use Cases
❑ Description of acceptance test cases or execution of test cases(documentation)
❑ The prioritization of test cases
❑ Test Automation
❑ Fit tables for the automation of tests
❑ Documentation: Project documentation is a critical basis?????
TDD

6. Disadvantages of Agile Testing
❑ There is no need of written documents in Agile method as it focuses on one-to-one communication over written
documentations.
KHAN, Rijwan; SRIVASTAVA, Akhilesh Kumar; PANDEY, Dilkeshwar. Agile approach for Software Testing process. In: 2016 International Conference System Modeling & Advancement in
Research Trends (SMART). IEEE, 2016. p. 3-6.

7. Advantages of Agile Testing
❑ Less Delivery Cost
❑ Because of Tight timeline and high expectation of customer: Agile seems best.
❑ It involves customer collaborations and short week cycles. It makes the project speed fast due to all these features
❑ It is best model for project where requirements are changing and project scope is not clear. It decreases the number of
defects in production and therefore it decreases cost of project as working product.
❑ When process became mature, less number of bugs
KHAN, Rijwan; SRIVASTAVA, Akhilesh Kumar; PANDEY, Dilkeshwar. Agile approach for Software Testing process. In: 2016 International Conference System Modeling & Advancement in
Research Trends (SMART). IEEE, 2016. p. 3-6.

8. TypesofAgileTesting
HELLMANN, Theodore D., et al. Agile Testing: Past, Present, and Future--Charting a Systematic Map of Testing in Agile Software Development. In: 2012 Agile Conference. IEEE, 2012. p. 55-63.

9. Free Agile Testing Tools
❑ Bamboo: Bamboo is a CI/CD server from Atlassian. Like Jenkins and other CI/CD servers.
❑ Selenium: is the most widely used test tool for browser test automation.
❑ Watir: Watir is an open-source testing tool made up of Ruby libraries to automate web application testing.
❑ Katalon Studio: Katalon Studio is a free automation testing solution developed by Katalon LLC. The software is built on top of the
open-source automation frameworks Selenium, Appium with a specialized IDE interface for API, web and mobile testing.
❑ Jmeter : Jmeter is an open source performance testing tool written entirely in Java
❑ SOAP UI
❑ VirtualBox
❑ Xmind: XMind in the most popular and feature-rich mind mapping tool. You can use it to create stunning mind maps to highlight the
features of a website, or to create a user journey flow through the application. Mind maps have become very popular in the world of
software testing because they provide nice visuals and can be of great help when designing test cases.
❑ Unit: Thoughtworks’ test runner
❑ Mockito: for mocking dependencies
❑ Wiremock: for stubbing out external services
❑ Pact: for writing Consumer-Driven Contract tests (CDC) tests
❑ REST-assured: for writing REST API-driven end-to-end tests
❑ FitNesse by Robert C. Martin et al.
❑ Robot Framework

10. Resources
https://dzone.com/articles/find-the-best-agile-testing-tools-for-your-team
https://www.pcquest.com/5-useful-open-source-testing-tools-for-agile-testers/
https://dzone.com/articles/top-10-automated-software-testing-tools
https://dzone.com/articles/the-life-cycle-of-agile-testing
https://dzone.com/articles/how-test-automation-supports-agile-transformation
https://dzone.com/articles/5-tips-for-agile-testing
https://dzone.com/articles/agile-testing-vs-traditional-testing
https://dzone.com/articles/how-agile-changes-testing-part-1
https://www.jrothman.com/mpd/agile/2016/03/how-agile-changes-testing-part-2/
https://testing.googleblog.com/
https://adtmag.com/articles/2018/04/11/agile-and-tranforming-qa.aspx
https://adtmag.com/blogs/watersworks/2020/01/jenkins-creator-software-testing-machine-learning.aspx
https://www.informit.com/articles/article.aspx?p=441115&seqNum=4
https://adtmag.com/articles/2018/04/11/agile-and-tranforming-qa.aspx
https://web.archive.org/web/20140305084801/http://blog.utest.com/why-agile-development-fails-sometimes/2012/11/
https://web.archive.org/web/20140209193430/http://blog.utest.com/
https://www.researchgate.net/publication/220694129_Software_Testing_and_Analysis_Process_Principles_and_Techniques/link/0deec525cf97c8d36a000000/download
https://www.thoughtworks.com/insights/articles/enduring-techniques-technology-radar?utm_campaign=ping&utm_medium=email&utm_source=marketo
https://martinfowler.com/articles/practical-test-pyramid.html
Hellmann, Theodore D., et al. "Agile Testing: Past, Present, and Future--Charting a Systematic Map of Testing in Agile Software Development." 2012 Agile Conference. IEEE, 2012.
Opelt, Kealy, and Tracy Beeson. "Agile teams require agile QA: how to make it work, An experience Report." Agile 2008 Conference. IEEE, 2008.
Khan, Rijwan, Akhilesh Kumar Srivastava, and Dilkeshwar Pandey. "Agile approach for Software Testing process." 2016 International Conference System Modeling & Advancement in Research Trends (SMART). IEEE,
2016.
Sureshchandra, Kalpana, and Jagadish Shrinivasavadhani. "Moving from waterfall to agile." Agile 2008 conference. IEEE, 2008.
Coutinho, Jarbele CS, Wilkerson L. Andrade, and Patrícia DL Machado. "Requirements Engineering and Software Testing in Agile Methodologies: a Systematic Mapping." Proceedings of the XXXIII Brazilian
Symposium on Software Engineering. 2019.
COUTINHO, Jarbele CS; ANDRADE, Wilkerson L.; MACHADO, Patrícia DL. Requirements Engineering and Software Testing in Agile Methodologies: a Systematic Mapping. In: Proceedings of the XXXIII
Brazilian Symposium on Software Engineering. 2019. p. 322-331.
Source:
SUMRELL, Megan. From waterfall to agile-how does a QA team transition. In: Proceedings of the Agile Conference (AGILE). 2007. p. 291-295.
KAUR, Kamaljeet, et al. Applying agile methodologies in industry projects: Benefits and challenges. In: 2015 International Conference on Computing Communication Control and Automation. IEEE, 2015. p. 832-836.

11. THANKS