Hot answers tagged

2

BDD Tests As many things around us - there is more hype around BDD than what it deserves. BDD was born as a way of naming your tests clearer: instead of saying that you test this-and-that you're saying it-should-work-this-and-that. And this is a great idea since it makes it clear about the purpose of the test and it allows the test to be shared with not-so-...


2

You probably have read that BDD is not about testing, but about improving communication. In software development, there are a manifold of ways to express the same thing; and some fit better for each role. Given that, it is common for a project to have many documents expressing the same thing. This cause two problems: When requirements change, all these ...


1

You should make more clear what you want to know because you mixed two things up. Let me give you some hints. On the one hand you want to know, how to do functional testing, especially black-box testing, to crash a (web) application. To achieve that you should perform negative tests. In your case, if you want to manipulate input fields, forms etc. you ...


1

I would suggest you not to bind any particular automation tools to your testing. Which means that at the test framework level, you need to have a shared layer as the interface to the test automation developers. While underline framework development could use any automation tool which works fine with different kinds of applications like web and win form. In ...



Only top voted, non community-wiki answers of a minimum length are eligible