Tag Info

Hot answers tagged

7

I think you answer this by asking, "Why do I need a build acceptance test suite?" There is no universal answer, but if your organization has a suite, someone should be able to answer the question. For example, in a previous job, the developers on my team frequently made changes that rendered the build unusable: it would not install, or it would crash as ...


7

I read two questions: (1) should we document the tester-written unit tests and (2) how should we treat tests that assume implementation details? It's important to distinguish between scaffolding and unit tests. (Please don't get caught up in my terminology; I'm just trying to make a point about some concepts.) Scaffolding is code a developer writes as ...


7

Your testers deliver the tests scenarios that should be implemented by the developers and some of your developers write more tests than required. Give them a raise! I recommend to review the extra tests and check if they make sense. Encourage all developers to write more tests to put their knowledge into tests. They know implementation details, so they can ...


7

Introduction (This should be brief, something like why we test our applications and why it's important) Scope and limitations of our Test platform Resources (Software ex Selenium, Test Scenarios, Links for tutorials) Procedures (How to register a bug or tests priority) But in general the documentation changes according to whom it is intended for, ...


4

I found this document based on IEEE-829 and have used it for rough guidance, but remove categories that seem like overkill for my team or merge categories that seem similar. Since I started doing this, I've received many compliments on the clarity of my test plans. I use a wiki for documentation, which makes it easy for users to jump to the sections they ...


3

In the traditional sense of the word a unit test is designed to test the smalled functional unit of software such as s single method or function. Unit tests are intended to provide limited testing of the functional capabilities of a function or method in isolation. Typically, unit tests are written and maintained by developers because they should be used by ...


3

I would say why only create a document. You can create a mind map or a any other visual representation of what are you trying to convey. Its a nice way to get your message across and won't cost you any words at all. I have used test strategy to communicate in essence, only the following things What you plan to do ? How you are going to do it ? If I am able ...


2

It's interesting that you mention it's important for as many people as possible in the organization to read and remember your test strategy. I infer that by default, people will not read or remember your test strategy. That tells me you want a document that is both instructive and persuasive. If you want someone to read all the way to the end, you ought ...


2

I have moved my team completely away from test strategy documents. We are using mindmaps instead as they paint a great picture of what you are trying to test and allow for quick conversations with development and analysts. You can then continue to flesh them out and move to test ideas. Excellent blog about this - ...


2

I can't promise that our techniques are state-of-the-art, but they gave us the level of confidence we needed and might give you some ideas for an approach. We made a backup of the production database before we made the fix, with all of its known duplications. We then ran the de-duping code against that database and analyzed the duplications it found to ...


2

Some of your developpers are probably doing a combined BDD/TDD approach as described in MSDN Magazine: BDD Primer - Behavior-Driven Development with SpecFlow and WatiN. I see unittests as a kind of executable documentation that fail if the documentation (=testcode) or the some productioncode (that is called by the testcode) is wrong. Do you consider ...


1

As the requirement is to move new feature test cases to build acceptance suite, I think it is important to note, what benefits the build acceptance tests provide usually: 1) Fast feedback to developers, if there are issues in the checked-in code 2) Tester gets a working build to start with their activities 3) Application should be usable every time Now ...


1

This sounds like the kind of thing where an entity-relationship style diagram or similar would help. If you want gold-plated, Visio does that. Simpler tools - you can do the same thing (with a bit of extra effort) in any drawing application, and I believe the Google drawing tools offer similar kinds of function. If I read this correctly, you're looking ...


1

I suspect the best representation for devising a test plan will not be the same as the best representation for visualizing the relationships. For devising a test plan for a combinatorial problem, I think you want a matrix and a list of constraints. The matrix has a column per independent variable, with the possible values of that variable listed in that ...


1

Along with understanding the need to have a build acceptance suite, which will help define parameters, I think the following things might universally apply: Don't pick atomic test cases, i.e. TCs that do only one thing. You've partly covered this in #3 of your question. You want TCs that cover a basic scenario that you consider absolutely essential for ...



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