SmartBear technical representatives are always ready to help with your product needs.
Test Management Test Automation
The Georgia Lottery Corporation (GLC) operates the state’s lottery system, which is used to enhance educational funding for the state. Since its inception, GLC has transferred more than $16.7 billion to the state education account, used primarily to help Georgia residents attend colleges and
The answer to “What is a Defect?” may seem obvious. Team members usually think of ‘defect’ as meaning something is wrong. But, how do testers really identify what’s wrong when testing a program? Are defects always incorrect behavior or can they be something unusual or
The agile manifesto suggests software teams should focus on working software over comprehensive documentation. That lead to the slow erosion of detailed specifications, and the rise of the poem-like snippet just above this paragraph. The example above is from classic story template format. These
With exploratory testing the tester builds their own map of a product, in the mind, and decides the appropriate places to go to get what they need to know. Not only that, the tester can change their mind, deciding to spend more time on one street and less on another. Think more Lewis and Clark, less
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?