Creating a Test Report for Embanet Interface
Not what you're looking for?
Produce a test plan for the following Interface according to the IEEE testing plan format
http://www.ruleworks.co.uk/testguide/IEEE-std-829-1998.htm.
Please see the attached document regarding the interface.
Purchase this Solution
Solution Summary
This creates a detailed test report for Embanet user interface.
Solution Preview
Question
Produce a test plan for the following Interface according to the IEEE testing plan format
http://www.ruleworks.co.uk/testguide/IEEE-std-829-1998.htm.
The Interface
The following is a simplified reference function inventory for the interface.
Primary and Secondary Functions
[First Class Login]
• User ID field
• Password Field
• Offline button
• Set Up button
• Login button
• Cancel button
Desktop
• File Menu
New
New document
New document special
New memo
New presentation
New address
Open
Close
Save As
Upload
Download
View File
Import
Export
Delete
Properties
Print
Exit
• Edit Menu
Undo
Redo
Cut
Copy
Paste
Clear
Find
Insert
Preferences
• Format Menu
Font
Size
Style
Color
Align
• Message Menu
New Message
New Message Special
Reply
Reply Special
Forward
Send
Send and Close
Unsend
• Collaborate Menu
Connect
Disconnect
List Connections
Change Password
Embanet.fc Setup
Directory
Who is online
Navigation
Add to address book
Add to Desktop
Add to Bookmarks
Permissions
Rules
Approve
About conference
Work offline
Private chat
• View Menu
View by icon
View by small icon
View by list
Explore
View by month
View by week
View by day
View today list
Split
Show deleted items
Change view properties
Line up icons by grid
Connect
Image
Smart zoon
Toolbars
• Help Menu
Contents
About this window
About FirstClass Client
You may use the annotated sample testing plan discussed below:
The following is an annotated sample testing plan outline following the "IEEE Standard for Software Test Documentation—IEEE Std 829-1998" (http://www.ruleworks.co.uk/testguide/IEEE-std-829-1998.htm).
1. Introduction. This section could have the following subsections:
a. Objectives: High level description of the scope, approach, resources, and schedule of the testing activities. It should also include a concise summary of the test plan objectives, the products to be delivered, major work activities, major work products, major milestones, required resources, and master high-level schedules, budget, and effort requirements.
b. Background
c. Scope: This section specifies the plans for producing updates to this software testing plan document itself and the methods for distribution of updates along with version control and configuration management requirements.
d. Reference
e. Definitions and Notations
2. Test items. The following documents need to be referred in this section: requirements specification, design specification, users guide, operations guide, installation guide, features, defect removal procedures, and verification and validation plans. The following subsections could be included in this section then.
a. Program Modules
b. Job Control Procedures
c. User Procedures
d. Operator Procedures
3. Features to be tested
4. Features not to be tested
5. Approach. Testing approaches should be described in sufficient detail to permit accurate test effort estimation. This section should identify the types of testing to be performed and the methods and criteria to be used in performing test activities. The specific methods and procedures for each type of testing should be described in details. The criteria for evaluating the test results and the techniques that will be used to judge the comprehensiveness of the testing effort should also be discussed. This section could include the following subsections:
a. Unit Testing
b. Integration Testing
c. Conversion Testing: Test whether all data elements and historical data is converted from an old system format to the new system format.
d. Job Stream Testing: Test whether the system operates in the production environment.
e. Interface Testing
f. Security Testing
g. Recovery Testing: Test whether the system restart/backup/recovery operations work as specified.
h. Performance Testing
i. Regression Testing
j. Acceptance Testing
k. Beta Testing
6. Pass/Fail criteria. One of the most difficult and political problems is deciding when to stop testing. The example criteria for exiting testing include (but are not limited to): scheduled testing time has expired (very weak criteria), some predefined number of defects discovered, all the formal tests have been executed without detecting any defects (tester may lose motivation under this criteria), or a combination of the above. This section may include the following subsections:
a. Suspension Criteria: when to suspend all or a portion of the testing activity on test items associated with the plan?
b. Resumption Criteria: the conditions that need to be met to resume testing activities after suspension.
c. Approval Criteria: The conditions for the approval of test results and the formal testing approval process. This section should also define who needs to approve a test deliverable, when it will be approved, and what is ...
Purchase this Solution
Free BrainMass Quizzes
Inserting and deleting in a linked list
This quiz tests your understanding of how to insert and delete elements in a linked list. Understanding of the use of linked lists, and the related performance aspects, is an important fundamental skill of computer science data structures.
Word 2010: Tables
Have you never worked with Tables in Word 2010? Maybe it has been a while since you have used a Table in Word and you need to brush up on your skills. Several keywords and popular options are discussed as you go through this quiz.
Javscript Basics
Quiz on basics of javascript programming language.
Basic Networking Questions
This quiz consists of some basic networking questions.
Basic Computer Terms
We use many basic terms like bit, pixel in our usual conversations about computers. Are we aware of what these mean? This little quiz is an attempt towards discovering that.