New answers tagged

0

A test plan details what, when, how, who, and more of a testing project. It should outline the general strategy and provide someone with enough information to allow them to get started whit the testing. After commonly being asked what details should be included in a test plan here at TestLodge, we have put together an example test plan based on the IEEE 829 ...


0

I am not sure about steps dependency management tool, but we can check if step def exits for scenario in a feature file. One way is to check is by having a dry run. @Cucumber.Options (dryRun = true) Dry run will ensures that you have step definition for your scenarios without actually running it. This approach may not work always, depending on how you ...


0

The short answer: Every test automation tool out there has some sort of test case management capability. So there's no need to list them down here. My approach: I find it easier to list my requirements and code a solution myself instead of using a 3rd party framework. Re-inventing the wheel is generally the better solution. Yes you read me right. Each tool ...


0

You can export the complete test cases to an xml file and then replace all Manual keyword with the Automated Keyword(You can do the bulk replace by using any of the text editor). Then again import these test cases to the test link.


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 ...


0

I don't try to differentiate between BDD and TDD and believe that they are both about the following: small change constant feedback continual improvement improved communication and they led to the following benefits: useful functionality based on real needs rapid change for features as needed less artifacts quick turnaround for bug fixing


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 ...


0

A Test Plan must have the minimum skeleton as specified below. It is very important to remember and know the difference. We are not referring to test approach or strategy documents here. I have always used Microsoft project to create and track a plan as it is such a powerful tool and provides such a wide variety of views that suits everyone i.e. if you want ...


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 ...


0

What about a wiki, or something like a wiki? I'm thinking specifically of the ability to include pages inside other pages, so you could make a change to one of the inner pages, and then have it reflected in all the containers. I believe you can do something similar with MS Word.


0

Yellow box testing- It is a message level testing. We can say that yellow box testing is the validation of alert messages. User can test that whether the application is correctly providing the alert messages. This is widely used technique in manual testing these days. Green Box testing- It is a testing process that exercises a software system's coexistence ...



Top 50 recent answers are included