Hot answers tagged

3

When is a good time to develop new automated test, and who should be responsible for this? Developing the structure of the automation can begin very early on in the process. Once the requirements are set the objects can start getting built out, be put into classes and a lot of the assertions can be built that way all that remains is ToDos that hook ...


2

What are the most important components/parts of a well-written test plan document for a testing project. Consider you are testing a Financial web app. As per IEEE 829 standards, the components of a Test Plan document should be : Test Plan identifier References Introduction Test Items Risks Items to be tested Features excluded for testing Testing ...


2

Strategy is automation. Could be: Brutal force: read all values on all pages to a field variable and compare each with it's neighbor. Simple task for test automation. Optimised: sequentional read of the parameter and compare with the previous and next value, regardless of independently switching to the next page, if you reach end of the list. Avoidance: ...


2

For Banking Applications : Banking applications are one of the most complex websites, from a testers point of view. They : Have loads of functionality (Money Transfers, Credit cards, Reports, Billing, Payments) Large Scale Integration- of the various functional modules listed above Complex Business Workflows Real time processing High rate of transactions ...


2

Info: These testcases are critical functionality. Judging by the above statement, I'd say you need to have both unit tests and UI automated tests (or integration as well depending on the architecture layer and systems integrated). However, there are pros and cons on using both (that mostly depends on the organization, engineer in charge of creating one ...


1

Based on: This application allows cash transfers from many different savings/checking accounts to a central account which corporation use to improve cash flow and liquidity and A customer can create/delete/update profiles(accounts) and can do a lot of other things I would make sure you have test cases that check: Account identifiers are for valid accounts ...


1

Probably you're talking about some kind of smoke testing. Usually it's done as a system/integration testing. Unit testing is a responsibility of every developer not a QA engineer. So if you're from testing team, the answer is using GUI tests for the whole software. If you develop some critical components, writing good unit tests are highly desired for your ...


1

100% assurance You will never be 100% sure, but sometimes testing in production will greatly improve your chances. What will you need ? Great feedback and telemetry from your real customers Somekind of A/B testing framework so you can remotely control which user uses what (this needs to be implemented both as a server side to control behavior and a ...


1

My rule of thumb when designing UI tests is to do a basic check that the UI works, but coverage of the exact logic really should be shifted further down the testing pyramid (this will save execution time, plus lower level tests are better suited to it). A simple check of the first and last elements should suffice. That said, if you don't have good coverage ...


1

You said you're using the Page object model to separate your Web code from your orchestration and assertions. Let's not lose that good design principal when designing this test. If you haven't already, abstract a table on your Web page into a collection (eg string[]) on your page object. Find out how to check a string[] is alphabetically ordered, which your ...


1

If all the results are on the same page, it should be pretty straightforward. You'll need to fetch the cell you've sorted, probably require a comparator of some kind, and just verify that each cell is ascending (or descending, as the case may be) from the previous cell. If you're using pagination it's going to be harder. You would need to go through each ...


1

As always, it depends. If the application developers have been building unit and integration automation that runs with each build, you aren't as far behind as you would be if no low-level automated checks existed. QA is usually in charge of automated GUI checks and may also be in charge of some of the high-level headless automated checks (such as API ...


1

Usually developers write unit tests (because unit tests are close to the code developers know well). Automated GUI test use different instrumentation (Selenium?) so need a bit different skillset. Sometimes might be even developed in different language: because GUI tests are inherently slower, it might make sense to use language like Python which allows you ...



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