If you were asked to write a test case, would you know what to do? What about a test script, or a test scenario? The first step is learning what these terms mean. Each of these terms implies a different level of detail and is used for a different purpose. Once a tester knows what each of these terms
How does your team come up a testing strategy? For many teams, the answer is "we don't", at least, not really. Instead the team does what someone else defined a long time ago, perhaps something like run all the test cases, and then rerun the tests that fail once there is a fix. Other
The engines were cranking away on creating and using agile development practices well before the manifesto was written and signed, but testing has been slower to catch up. For a long time, if you asked about the role of an agile tester, the response would be 'collaboration'. Collaborating
Functional testing is great for finding some types of problems. But using that technique alone is a bit like volunteering to put blinders on to other risks.
How do we test the product to find problems that only show up when all the pieces are combined and in the right place?
How will Selenium keep up with all these changes?
Under agile software development, a delivery team is expected to have everything it needs to deliver software as one team. That means the developers, testers, DBA's and analysts are all on one delivery team, working together to ship a stream of value. The focus shifts from work-product as a
In this webinar, Nikhil Kaul, Product Manager, joins Engineer, Rick Almeida, to discuss how to balance the trade-off between achieving high test coverage and testing code and requirements that matter.