Tag Info

New answers tagged

0

Hexawise is one of several tools that could help you: Identify all the potential configurations for a given system Identify a prioritized set of permutations that maximize coverage (based on user-specified coverage objectives). As dzieciou mentioned, and provided links to above, multiple tools can do this. Disclaimer, I am the CEO of Hexawise. Having ...


1

I would separate the test case into 2: The first one ends with the confirmation message and the second one continues from there on. I would create a bug, link it to the first test case and keep the test case in 'ready', while I would close the second test case. If this is not a major requirement for you, then the test cases can be prioritized, so that ones ...


2

If you have specifications that say a confirmation must be displayed, the test fails. If you have user requirements or user expectations that there will be a confirmation dialog, the test fails. In the situation you describe, I would create a bug from the test, but it would have a lower severity rating because it doesn't interfere with functionality. The ...


1

It may depend on the strategy of your project, but i'd say this test is failed. If the confirmation is part of your specifications/functional need, you can't make this test pass. Imagine this is the only issue in your whole test plan, if you pass the test, then your indicators will be all green for this functionality. Thus, there is no reason to do rework, ...


0

Got an article on website testing methods and would like to share hope this might give you some ideas on what to consider while testing any simple website. Here's the link - http://blog.testing-whiz.com/2013/12/website-web-application-testing.html


0

loading(how long to load the page): 1)How page loads based on different internet speed. 2)Loading time in different browser,OS. adaptive(to different browser): Here we do compatibility testing as page shown behaves under 1)Different browser(safari,chrome,IE,firefox).Different versions of browser. 2)Different Operating system


1

Answer:Test cases should be atomic to the component you are testing. So write a test case for each field. Reasons: Problem in counting execution completion status: During test execution, if the first name field works and last name field does not work you will have to fail the test case. which is not correct because the first name field still works.This is ...


0

MBT would not work. Reason: You claim that you domain knowledge is quite limited. Its hard to model something that you do not understand. BDT may work but will not be complete. Reason: With limited knowledge of the domain means you might not be able to identify all users & business processed. No testing documentation means you do do not have a way of ...


0

I have wrestled with this problem a number of times. For instance, I have had a number of occasions where I needed to hand each member of a group of testers a stack of paper to describe the steps they had to take. The first time a tester needs a detailed procedure it has to be there for them to read immediately. Similarly, when the procedures are very ...


1

Since you have said it yourself that having separate documents may add to tester's time, wouldn't it make sense to have a checklist instead of such vast and mostly not so easy to read documents. The checklist can be used for testing and whatever information is gathered during testing can be properly formatted in a document so that the intended stakeholder ...



Top 50 recent answers are included