A test plan is a tool you use while planning a period of testing. It basically describes what will be tested, who will do it, where they will do it, and how they plan on doing just that. In some coorperations, where law and contracts are really important, test plans are usually the size of a small child, and nobody ever reads it. Apart from lawyers. That's because test plans aren't always made for you - they can also be made for your team or for different stakeholders.
I've gone through several iterations of coming up with test persona names in my latest project. In the beginning I started thinking about names for my amusement. But after some time I realized that there's…
Last month I did a one-week project where I put an app through usability testing. The company that hired me was very careful not to tell me a lot about the app and their system, since they wanted me to see it for the first time. That was a very wise decision on their part. While I performed the first testing, and got to know the app, I was struck with the value of this very first meeting with the system.
I've only recently gotten to know databases. How they work, SQL and the different scripts you can use. I love it. I think it's so much fun going into different databases when testing, viewing, comparing, joining and editing them. Even though the amount of trouble you can cause in there is immense.