I'm in the process of completing the acceptance testing with a customer for a web based system and after 3 rounds of acceptance testing we have found that one particular feature of the system does for some reason not work on the clients 2 machines we have used for testing.
It is pretty unusual for a browser based application and we have gone through an in-detail compare of the computers and the test environment. There are also possible programming problems that may exascerbate the problem
Unfortunately a lot of other things have gone wrong in the project as well, and this has contributed to a loss of trust and made acceptance testing very tedious.
I'm looking for ways to manage this better in the future, apart from of course identifying the actual difference that is causing this.
Can people here recommend project management and contractual preparations that are realistic for this scenario? The applications target market is only about 100 people with the 2 key people at the client obviously being super admins of the system.
- my business partner thinks its too hard a requirement to force acceptance testing as complete if only tested on a platform like browserstack.com - what do other people think
- should I include the right to force a memory test or other IT checks on the desgnated test equipment?
- or is this simply something that can happen, bad luck?