I am a web developer at a full service marketing firm. We have a relatively small development operation but we build websites for global clients. We just completed development on a new website for one of our larger clients, the CEO and the board approved the site and we are ready to launch. The problem now is that someone high up in their IT department is now demanding to see website test results/documentation.
This is not something that we have ever ran into before. Is there some sort of standard documentation that we should be keeping through the testing process?
We do not pay an outside firm to perform any formal QA testing done on the website but our testing process is much better and more robust than any other firm that I have worked at. We track a number of our bugs, and we could show them some of what we have fixed, but we do not document everything as that would eat into our efficiency.
I am confident that the website will perform well, especially as their old website (that they are running now and we did not build) is riddled with bugs, errors, performance issues, security nightmares, and lives on GoDaddy's shared hosting.
We will continue to manage this website after it has launched, so the person questioning this will not really have any involvement in the website at all.
Has anyone else run into something like this? Is there a system/process that we should use in the future to track these kinds of things?