irFANTASTIC
Member
Reged: 05/10/06
Posts: 63
Loc: Mumbai
|
|
What are test cases to be written for a Acceptance Testing for a genric software.
In my organisation I need to prepare Acceptance Test cases which should be executed to finally approve the build.
Kindly give some light on this topic.
|
JakeBrake
Moderator
Reged: 12/19/00
Posts: 15290
Loc: St. Louis - Year 2025
|
|
You should be able to establish those based upon use cases and architectural design documents - correct?
|
irFANTASTIC
Member
Reged: 05/10/06
Posts: 63
Loc: Mumbai
|
|
Thanks. Can you please give a short example that would make things easier for me
|
SumitJaitly
Junior Member
Reged: 04/17/03
Posts: 124
Loc: OneWorld
|
|
These have to be very basic test cases for snaity testing. Like Add, edit/update, delete etc are working. This will depend upon your applications basic functionality. Also check the previous questions on smoke test, BAT etc in the forums.
Sumit Jaitly http://sumitjaitly.rediffiland.com/iland/sumitjaitly.html
|
vkon2005
Member
Reged: 12/27/06
Posts: 28
|
|
Hi irFANTASTIC,
Firt make sure to write Acceptance Test cases for main functionalities that are frequently used by the user.Concentrate on them.
The Use Cases created during the Requirements definition phase may be used as inputs for creating Test Cases. The inputs from Business Analysts and Subject Matter Experts are also used for creating.
We cannot give examples for this particular questions. Because it all depends on project.
Good Luck vkon2005
|
Vipul_Vashisht
Member
Reged: 09/05/06
Posts: 68
Loc: New delhi, India
|
|
Concentrate on the business case scnerios that the end user would normally walk through while writing test cases for UAT.
make double sure that the scnerios are working in test environment prior to moving to UAT.
all the best
Vipul Vashisht
|
Manjula_23s
Member
Reged: 07/04/07
Posts: 74
Loc: Karnataka,India
|
|
Hello All, Is Acceptance testing required for a Open source Projects
-------------------- Manjula
|
thinktest
Junior Member
Reged: 04/17/06
Posts: 25
Loc: leeds
|
|
Few hints that i wrote in my spreadsheet. Are all fonts, colors, shading and toolbars consistent with standards and UI guidelines? Are all colors are consistent with standards and UI guidelines? Are all shading consistent with standards and UI guidelines? Are all toolbars consistent with standards and UI guidelines? Are spellings Correct? Are all the Brand logos positioned in the right location? Is the help module available on all the Landing hub pages? Are all date formats correct (dd-mm-yyyy)? Are the date edits being correctly applied? Does all text wrap when displayed in the text editor? Is there a scroll bar on every applicable block? Is the Toolbar List button enabled only when a list of values is available for an item? Do the window titles correctly identify each module? Is there hint text available for all applicable items ( place the cursor on each component)? Do all of the initial 'window display' sizes fit entirely on the screen (assuming an SVGA 1024 x 786 resolution)? Are the correct items case sensitive? (i.e. Do fields allow lower case text if they should only accept upper case?) Are error, warning and information messages accurate and understandable? Do all Move Up and Down operations display when clicked? Are the Landing hub page titles order correct? Are the appropriate edits done on all fields (range of values, valid values, on different paragraph systems.) Are defaults appropriate? Are the correct fields mandatory? Is the tool bar present and appropriate buttons enabled? Are screen & field labels appropriate? Are fields & buttons ordered appropriately? Are all codes valid? Are all field labels are consistent across the application Do all drag and drop modules work consistently? Clicking a link takes you to the appropriate information or page. Ensure the accuracy of breadcrumbs by clicking down to the lowest page levels on the site. Determine that formatting is consistent throughout the site (Tabs, headers, Toolbars) Verify that text headings are consistent with text content (Tabs, headers, Toolbars) Be sure that all text is complete, not cut off or missing Check for spelling errors, typographical errors and grammatical problems. Verify that all images have alt tags (hidden text accessible by a text reader that identifies what the image is).
-------------------- Everything you can think of can be subject to test!
|
Peter Ruscoe
Veteran
Reged: 03/18/02
Posts: 7686
Loc: Tampa Bay
|
|
thinktest, your list includes a large number of areas that, while valid, have nothing to do with usability or accessibility testing.
That, along with the fact that you have revived a number of fairly old threads (includes this one), prompts me to suggest that you think before you post, and don't just jump in everywhere that you think you might want to provide information.
Having said all that, this topic didn't really belong in this forum anyway.
|
boozehag
Newbie
Reged: 08/12/07
Posts: 17
|
|
Quote:
Hello All, Is Acceptance testing required for a Open source Projects
depends on whether you want to ensure the software is useable or not.....
|
musaffir87
Newbie
Reged: 05/21/11
Posts: 3
Loc: Bangalore India
|
|
Hi, if you are still looking for an answer pls go ahead and read my opinion 
It should be all about covering from end to end of your app/ system..
you should write test scenarios which covers the entire functionality of the app... which should include all the critical business flows...
if u belongs to the end users coomunity of the system u must be the best person to design ur test suite...
cover all the posative scenarios and also u can do some r&d on the system to know how all u can break it..ultimately ur aim should be to break the application some how..
please let me know if u differ or agree to me...
-------------------- ~Musa
|