Test Cases for lotus application

What is the Procedure followed for testing the lotus application.if any one doing testing for lotus application. Please give me some guidance

Thanks in Advance

Subject: Test Cases for lotus application

IMHO same as for any formal testing of any application.

You look at the requirements, devise a test script to test each of the requirements are met, then follow the script.

You will need some test user ids representative of each access level / role in the database for effective testing.

HTH - Rufus.

Subject: RE: Test Cases for lotus application

first thanks for your response Rufus.

If you have any sample test cases or templates which you are following can u send me apart of that to my mailid.

if you dont feel any problem.

my ID:ratna_2u@yahoo.com,rajendravr@drreddys.com>

Subject: RE: Test Cases for lotus application

I’m unable to send you any of my existing scripts as I don’t have the intellectual property rights on them.

TBH I don’t think they would be of any use to you are they are specific to the application being tested rather than generic.

Generally speaking each script consists of a number of pages each one testing a specific requirement:

Requirement: Usually a reference to a section of the specification i.e. S1.2 - Client Security

Overview: A brief summary of the test, usually an expansion of the requirement and how it will be tested. e.g. Create various documents and ensure that users are only able to edit documents they create, view documents that other members of their department have created, and are unable to view documents from other departments.

Preparation: A step by step summary of the test data that needs to be created i.e.

  1. Using UserID A1 create a document (1) for Department A.

  2. Using UserID A2 create a document (2) for Department A.

  3. Using UserID B1 create a document (3) for Department B.

Tests:

A table showing the specific test, expected result, Pass / Fail and Notes. i.e.

Test 1: Using UserID A1 check if document (1) appears in the view,

Expected Result: Document should be visible.

Outcome: Pass

Notes: none

Test 2: Using UserID A1 check if document (2) appears in the view,

Expected Result: Document should be visible.

Outcome: Fail

Notes: Only documents created by UserID A1 appear in the view.

And finally a Name, Date and Signature space on the bottom to say when that test was carried out.

This is a labourios and paper intensive testing and usually only needs to be done when you need to prove that the system has been tested and delivered to be user requirements. By scripting tests it makes it easier to retest once bugs are fixed and carry out regression tests (proving that a bug fix hasn’t broken anything).

HTH - Rufus.

Subject: RE: Test Cases for lotus application

Thanks Rufus for your information.Is there any automated tools for testing lotus application.I designed my own test case if u want me to send. I will send it.