Shreya2603
Member
Reged: 11/25/07
Posts: 69
|
|
Hi all,
Actually a major discussion is going on regarding Test case Format in my company and the reason of discussion is that it should be in Excel or Word..?
Ratio for both are 50-50, as some find Excel more suitable & some find word, so management asked us to research. So can u guys help me to find out?
Just wanted to know that wether your company is usin Excel or word.
It would be really great if you can help me in some of the fields you are using in your Test Case Documents. 
Thanks in advance...!!!!
--------------------
Thanks & Regards
Shreya
|
JakeBrake
Moderator
Reged: 12/19/00
Posts: 15264
Loc: St. Louis - Year 2025
|
|
Shreya,
50-50 across Word and Excel? Did no one mention a database? What about Lotus 123, WordStar, or Word Perfect?
If it is down to Excel vs Word, consider the top 3 (IMO) advantages of using Excel:
1) Excel can be queried just as a database.
2) Excel can calculate without custom VBA.
3) Excel files can be output in many different formats for use by other tools.
Consider the example under this link.
|
BharathkumarPenimall
Member
Reged: 07/20/07
Posts: 29
|
|
in my organization we are using excel
http://groups.google.com/group/testing-certifications?hl=en
Regards,
Bharath
www.testbharath.wetpaint.com
www.whytesting.blogspot.com
|
Shreya2603
Member
Reged: 11/25/07
Posts: 69
|
|
Forgot to write that I am talking about manual Testing
--------------------
Thanks & Regards
Shreya
|
JakeBrake
Moderator
Reged: 12/19/00
Posts: 15264
Loc: St. Louis - Year 2025
|
|
... and what is your point??? There is nothing discussed here that excludes manual tests.
|
Shreya2603
Member
Reged: 11/25/07
Posts: 69
|
|
yes..I only added this line to complete my given information as  I am expecting more answers to my query.
--------------------
Thanks & Regards
Shreya
|
AOQA
Active Member
Reged: 04/12/07
Posts: 1044
|
|
We're using Excel, and it has a couple of advantages: specifically, we have a couple of columns that group the cases in various ways (by result, by iteration) and Excel's Validate and Autofilter functions allow for easier manipulation of the test cases.
|
pearl_qa
Member
Reged: 06/11/07
Posts: 32
Loc: NoVA, USA
|
|
Another vote for Excel ... I've used Excel in several organizations where the company didn't have any formal tools in place. I find it much easier to use than Word since you can generate metrics for individual worksheets and the entire test case workbook using Pass, Fail & Not Run values in the test case results field. You can also add columns to link each test case to System and Software Requirement numbers. You can then sort or filter the test cases by requirement number to get the requirement coverage for a particular requirement.
The only time that Word-style test cases were more useful was when the client required use case style documentation instead of individual test scripts (which ended up being a collection of test steps grouped into a larger use case) with descriptions of the functionality, entrance/exit criteria, detailed test steps, environment configuration info, requirement text and time estimates for each use case as a whole. It makes it easier to read for non-testers in that style but it's harder to get a current overall status.
|
brentpaine
Veteran
Reged: 03/09/07
Posts: 3754
Loc: Waterloo, Ontario, Canada
|
|
I have to agree with Jake on this one. Another nice advantage to Excel is that, if you already have the information in Excel, you can use VBA in order to create macros to do all sorts of wonderous things for you, like create new sheets, even in their own documents, generate a results matrix, automatically generate a new worksheet containing reports on the results matrix you just created, etc., etc., etc.
Now I'm not going to say that Word doesn't allow you to create macros too, but for the purposes of testing, Excel is much easier to work with when it comes to interacting with the data. After all Word is a word processor. So if you are looking for a way to record your test cases, that might be perfect for you. However, if you look a little further ahead you should be able to forsee some difficulties or limitations with it also.
Really, I don't understand the arguement FOR Word here. Can you explain some of the arguements you're getting in favor of Word?
--------------------
Brent
--------------------
9 out of 10 people I prove wrong agree that I'm right. The other person is my wife.
--------------------
What is Holistic Testing?
|
Joe Strazzere
Moderator
Reged: 05/15/00
Posts: 10116
Loc: Massachusetts, USA
|
|
Quote:
Just wanted to know that wether your company is usin Excel or word.
We use both.
The main portions of test plans are always written using Word.
Occasionally, we'll use some Excel spreadsheets as well.
--------------------
- Joe
I speak only for me. I do not speak for my employer, or for anyone else.
Visit my new blog All Things Quality
|
DSquared
Moderator
Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
|
|
Let's go back to the requirement. The requirement is to document the steps needed to successfully test some functionality.
Not sure if format of that documentation really has an effect on the base requirement or not. I would say not. Therefore, are you arguing over a very low priority issue when the real issue is to document the test in the first place?
|
Shreya2603
Member
Reged: 11/25/07
Posts: 69
|
|
Thanks all..As your information will really help me..
--------------------
Thanks & Regards
Shreya
|
hary
Newbie
Reged: 12/04/07
Posts: 1
|
|
Post deleted by Administrator
|
DSquared
Moderator
Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
|
|
Hary - please read the forum rules regarding "hijacking".
Regarding your question - did you try google?
|
Arshpreet
Member
Reged: 09/18/07
Posts: 72
|
|
In my company we used Excel.
|
Jasper175
Newbie
Reged: 01/24/08
Posts: 3
|
|
ALL - We were using MS Mercury and frankly I hate it because it's just cumbersome.
So someone designed and Excel concept and I didn't like it so I changed to make it more test friendly with some bells/whistles.
BUT lets face it - we want things to be simple, we don't want to click through tabs and the type of testing I do I base it off the Bug or Enh. # and create Scenario in the word Doc. I don't have to worry about failing each step there really is no need. If it fails you're not going to move on - you'll Bug-It , Note it and move on.
So my vote is for WORD. It's easier!
HOWEVER - anyway anyone can send their template? I'd like to see what other people do. It's obvious there is no industry standard except in various headers of TC.
|
blueinatl
Active Member
Reged: 10/20/06
Posts: 747
Loc: Atlanta, GA
|
|
Quote:
BUT lets face it - we want things to be simple, we don't want to click through tabs and the type of testing I do I base it off the Bug or Enh. # and create Scenario in the word Doc. I don't have to worry about failing each step there really is no need. If it fails you're not going to move on - you'll Bug-It , Note it and move on.
If a step in my test script fails, I don't cease to continue. Unless it is a critical bug that prevents me from moving to the next step in the script I would continue with the script (after logging the issue of course) so that I can identify as many bugs early in the process. I certainly don't set the script aside unless something is preventing me from continuing.
|
Richard_Hunter
Member
Reged: 08/16/04
Posts: 342
|
|
Quote:
If a step in my test script fails, I don't cease to continue. Unless it is a critical bug that prevents me from moving to the next step in the script I would continue with the script (after logging the issue of course) so that I can identify as many bugs early in the process. I certainly don't set the script aside unless something is preventing me from continuing.
100% agree, no point in stopping at step 5, waiting for the fix, running step 6 and finding that it fails there in a similar place in the code which could have been fixed at the same time.
Back to the question, Excel for me from the choices for the simple reasons already stated, Word is not really an option other then making it a pretty document.
--------------------
Richard Hunter
|
SteveHeidstra
Member
Reged: 10/28/04
Posts: 265
Loc: The Netherlands
|
|
Well we use either word or excel, to the testers preference. We have templates containing the HP Mercury plugin. After completion, the scripts are loaded into TD/QC with 1 click and then run from there.
|
yagsy
Advanced Member
Reged: 11/26/01
Posts: 563
Loc: San Diego, CA
|
|
Excel is my preference. I think it makes the overall test cases much more readable, quick and easy. Word tends to be, well, wordy. I don't like reading paragraphs for my test cases. I want one or two sentences of a description of the case and the steps listed out. I also like Excel functionality, and find it easier to add and subtract information, create corresponding documents. It's about pure convenience for me.
--------------------
Going out of your comfort zone requires failure. True genius is measured by your recovery.
...Jean Ann
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
