According to the Agile Testing: A Practical Guide For Testers And Agile Teams1, security and performance testing are two types of nonfunctional testing that are important for agile teams. Security testing ensures that the system is protected from unauthorized access, data loss, or corruption. Performance testing measures how the system responds to different levels of load, stress, and concurrency. These types of testing can be done at different levels of granularity, from unit testing to system testing, and can use tools such as JMeter, LoadRunner, or Selenium.
Story testing is a type of functional testing that verifies that the system meets the acceptance criteria of each user story. User stories are short descriptions of the features or functionalities that the customer wants from the system. Story testing can be done by the developers, testers, or customers, and can use tools such as FitNesse, Cucumber, or SpecFlow.
Tests based on behavior and test-driven development are two approaches that support agile testing practices. Behavior-driven development (BDD) is a technique that uses natural language to describe the expected behavior of the system in different scenarios. Test-driven development (TDD) is a technique that involves writing the tests before the code, and then refactoring the code to make the tests pass. Both BDD and TDD help to clarify the requirements, design the system, and ensure the quality of the code. They can use tools such as JUnit, NUnit, or RSpec.
[: (Professional in Business Analysis Reference Materials source and documents), Agile Testing: A Practical Guide For Testers And Agile Teams, Lisa Crispin and Janet Gregory, Addison-Wesley Professional, 2009, Scrum Testing: A Detailed Guide to Testing on an Agile Team, Testim, Accessed on January 29, 2024, Agile Testing Best Practices & Why They Matter, Atlassian, Accessed on January 29, 2024, , ]