Inserting validation in Data Driven Tests
I am working on a testing tool that provides image comparisons. For test data insertions, I am using excel and csv files that supply the tests with text that is used by the tool to mock actual user interactions – in filling up of forms/screens in the tests.
After the insertion, there is a need for verification to ascertain whether the test has functioned properly or not.
How would you test Google Maps “Get Directions” feature?
(I imagine this would be a good interview question, but in my case it’s more pragmatic than that.)
User Acceptance Testing Defect Classification when developing for an outside client
I am involved in a large development project in which we (a very small start up) are developing for an outside client (a very large company).
Isolating test data in acceptance tests
I’m looking for guidance on how to keep my acceptance tests isolated. Right now the issue I’m having with being able to run the tests in parallel is the database records that are manipulated in the tests. I’ve written helpers that take care of doing inserts and deletes before tests are executed, to make sure the state is correct. But now I can’t run them in parallel against the same database without uniquely generating the test data fields for each test. For example.
Acceptance tests for large multi-step online form
I have to extend/fix a large online form written by other developer. There is a lot of code, mixing PHP and JS. It’s kind of write-only style of coding and I want to redo it completely, but currently I can’t.
How to test the same software on all products in a product line?
In my team we have been working on a firmware for a product. The product was released some years ago but we still implement new features in the firmware and regularly provide a new firmware for our customers. Recently we have developed a new product which use the same firmware as the first one. Of course, we had to change the firmware to allow for some new capabilities (while still keeping functionality for existing product intact).
Functional testing and Acceptance testing leading to redundant code
What I know is:
Randomness in Acceptance-Tests
I’ve got a simple authentication solution, where a user can log in with either email or username.
Requirement gathering in an agile methodology
In the great book User Stories Applied the author specified the following process for trawling requirements in the form of user stories:
Agile User Stories and acceptance criteria
I am writing some agile user stories and acceptance stories for the first time, and was hoping for some feedback from an experienced product manager or developer.