I think that any functionality developed, either described in requirements, use cases, user stories or not described at all, regardless of development model needs to be tested anyway. DevOps or not. That is if quality and usability for end user is important. For that to happen I believe there ought to be at least someone developing and maintaining a test strategy and holding the test execution together. Then the actual testing can be done by developers within the team, or by dedicated testers.
Testing is needed in any type of model, strategy or process. When developing software, there should be test activities performed in order to validate that the features are correctly working as specified by requirements, there are no regressions introduced and generally, to verify products quality. Of course, it can be done by any team member (not only testers) but testing activities must be included in any software development type.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic.
Learn Exploratory TestingYou Don't want to Miss this Event
Learn the basics of Exploratory Testing in this insightful session
Privacy & Cookies
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.