Commonly Used Worksoft Functions

Below are the few worksoft functions which are commonly used:

1. Is Blank : This method is used to check whether a row is blank or not in a table / grid

2. Is Not Blank : This method is used to check whether a row is not blank in a table / Grid.

3. Search Empty Row : Method is used to search for an empty row in a Table / Grid

4. Select Node : Method is used to select a particular Node in the application

5.StoreProperty : Method is used to store particu;lar property value of an object

6. Store Parameter : Methos is used to store a particular value from a message / status bar message

7. Verify : Method is used to verify particular value in a table or any object

8. Click : Method is used to click on a particular object / at particular position

9. Press: Method is used to press a particular button / link

10. Input : Method is used to input a value in a table or textbox etc

Software Testing Manual And Automation: How to Access Worksoft Certify?

Software Testing Manual And Automation: How to Access Worksoft Certify?: Click Start and Point to All programs Point to the Worksoft folder Point to the Certify folder Select Worksoft Certify - Login dialog ...

How to Access Worksoft Certify?

1. Click Start and Point to All programs
2. Point to the Worksoft folder
3. Point to the Certify folder
4. Select Worksoft Certify - Login dialog box appears
5. Type in Username and Password
6. Click OK.

Worksoft Certify Architecture

Worksoft Certify Architecture:
Certify maintains an inventory of all of your applications and Business process certification components.Structure ties all of the components into a consistent hierarchy.

Certify organizes your application and business process components in a structured Hierarchy.
A Project is a collection of Variables, Processes, Layouts, Recordsets, Requirements and Test Results.
Each project is independent, and Information is not shared between them.

An Application is a set of Maps for Windows and Objects. Application can be available in one or more projects.
Users are given access to projects.A user may be authorized to read and write everything in on project, but can only read aspects of another project.

There are four Primary areas in this life cycle.

Components represent what you are planning, designing and building in Certify.

DataBase represents the repository where documented components are stored.

Applications represent the type of application being tested.

Data Analysis represents the data for your certification.

Worksoft Certify Life Cycle

Worksoft Certify Life Cycle:
Below are the Phases in Worksoft Certify Life Cycle

• Plan
• Design
• Build
• Test
• Analyze
• Maintain

Plan:
In this Phase, below are the tasks that will be done

•  Identify applications for Test and
• Identify End Users and
• Capture Business functions

In Certify, Create Applications and Versions. Get Project Requirements

Design:
In this Phase, below are the tasks that would be done

• Adopt naming standards,
• Define critical business tasks and
• Define Operating Cycles.

Build:
In this Phase, below are the activities that should be done.

• Create MAP
• Learn and Import / Resolve
• Interfaces
• Variables
• Processes
• Recordsets

Test:
In this Phase, below are the activities that should be done

• Automated or Manual execution
• Result Viewer

Analyze:
In this Phase, below are the activities that should be done

• Result Viewer
• Queries and Reports

Maintain:
In this Phase, below are the activities that should be done

• Import
• Resolve and Processes
• Interfaces
• Int

Types of Defects in Software Testing:

Types of Defects:

1) User Interface bugs (Low Severity):

• Spelling mistakes(High Priority)
• Important Alignment(Low Priority)

2) Boundary related bugs (Medium Severity):

• Doesn't allows valid type(High Priority)
• Allows invalid type also(Low Priority)

3) Error Handling bugs (Medium Severity):

• Doesn't Provide error message window(High Priority)
• Improper meaning of error message (Low Priority)

4) Calculation Bugs (High Severity):

• Final Output is wrong (Low Priority)
• Dependent Results are Wrong (High Priority)

5) Race Condition Bugs (High Severity) :

• Dead Locks (High Priority)
• Improper order of services (Low Priority)

6) Load Condition Bugs (High Severity):

• Doesn't allow multiple users to access (High Priority)
• Doesn't allow customers accepted load (Low Priority)

7) Hardware Bugs (High Severity):

• Doesn't handle device (High Priority)
• Wrong output from device (Low Priority)

8) ID control Bugs (Medium Severity):

• Logo Missing, Wrong Logo, Version No Mistake, Copyright window missing.

9) Version Control Bugs (Medium Severity):

• Differences between two consecutive build versions

10)  Source Bugs (Medium Severity):

• Mistake in Help Documents - Manual Support.

VBScript excel Methods

Below are the few commonly used VBScript Excel  methods / functions

1) GetSheetCount : Returns the total number of sheets in the run-time data table

2) Import Method: Imports the stecified microsoft excel file to the run-time data table
Syntax : DataTable.Import(Filename)

3) ImportSheetMethod: Imports a sheet of a specified file to a specified sheet in the run-time data table.
Syntax: DataTable.ImportSheet(Filename, sheetsource, SheetDest)

4) SetCurrentRow Method: Sets the specified row as the current(active)row in the run - time data tabe.
Syntax:DataTable.SetCurrentRow(number)

5) SetNextRow Method:Sets the row after the current(active)row as the new current row in the run-time data table.

6) SetPrevRow Menthod:Sets the row above the current(active)row as the new current(active)row in the run-time data table.

List of Testing Documents

Below are the list of Testing Documents.

1. Test Policy
2. Test Strategy
3. Test Methodology
4. Test Plan
5. Test Cases
6. Test Procedure
7. Test Script
8. Defect Report
9. Final Test Summary Report.

Test Policy is documented by Quality Control.
Test Strategy and Test methodology are document by Quality Analyst or Project Manager
Test Plan document is developed by Test Lead.
Test cases, Test procedure, Test script & defect report are documented by Test Engineers.

Test policy and Test Strategy are company level documents.Test methodology, Test Plan, Test Cases, Test Procedure, Test Script and Defect Report & Final Test Summary Report are Project Level Documents.

What is Software Development Life Cycle?

Software Development Life Cycle:
Stages involved in software project development

1) Information gathering, customer requirement
2)Analysis, Customer requirement v/s Solutions
3)Design, Dividing the project into modules & coupling them
4)Coding, Physical development of the project
5)Testing
6)Maintanance

Information Gathering:
In this stage, Business Analyst studies the requirement of the client / customer and they prepare the Business requirement Specification documents.

Analysis:
In this stage, Sr.Analyst prepared software requirements specification document with respect to corresponding BRS document. This document consists of two sub-documents,
 system requirement specification and Functional Requirement specification

Designing:
In this stage, Designers creates two documents
High level document and Low level document
HLD consists of main modules of the project from root to leaf and multiple LLD
LLD consists of sub - modules of main module along with data flow diagrams, ER-Diagrams etc are prepared by technical people.

Coding:
In this stage, Development team starts the coding for the project and develope the software.

Testing:
In this stage, Testing team tests the software that is developed by the development team by preparing the test cases.

What is Software Quality and Software Quality Assurance?

Software Quality:
Software satisfies quality when it meets the customer Requirements / Customer Satisfaction / Customer Expectations. Meets Customer Requirements refers to proper output & Customer Expectations refers to extra characteristics , good interface , speed, privacy, security , easy to operate, good functionality.

Software Quality Assurance:
SQA are the concepts to be followed by company to develope the software. An SQA team is responsible for monitoring & measuring the strengthof developing processes.

What is a Verification and Validation?

Verification:

Verification Typically involves reviews and meetings to evaluate documents , plans , code, requirements , and specifications. This can be done with the checklist , issues lists, walkthroughs, and inspection meetings.
Verification asks "Is the product being built right?"

Validation:

Validation typically involves actual testing and takes place after verifications are completed.
Validation asks "Is the right product being built?"
The term "IV and V" refers to independent Verification and Validation

What is White Box testing and its uses?

White Box Testing:
Testing control structures of a procedural design. Can derive test cases to ensure:

All independent paths are exercised at least once.
All logical decisions aare exercised for both true and false paths.
All loops are executed at their boundaries and within operational bounds.
All internal data structures are exercised to ensure validity.

Why do white box testing when black box testing is used to test conformance to requirements?

Logic errors and incorrect assumptions most likely to be made when coding for "special cases:, need to ensure that these execution paths are tested.
May find assumptions about execution paths incorrect, and so make design errors. White box testing can find these errors.
Typographical errors are random. Just as likely to be on an obscure logical path as on a mainstream path.

What is a Test case and Software project Test Plan?

Test Case:
A test case is a document that describes an input, action or event and an expected response, to determine if a feature af an application is working correctly. A test case should contain particulars such as test case identifier, testcase Name, objective , test conditions/ steps, input data, steps, and expected Results.

Software Project Test Plan:
A software project test pla is a document that describes the objectivies , scope and approach and focus of a software testing effort. The process of preparing a test plan is useful way to think through the efforts neede to validate the acceptability of a software product. The completed document will help people outside the test group understand "why" abd "how" of product validation.

Different Software Life Cycle Models

A software life cycle model depicts the significant phases or activities of a S/W project from conception until the product is retired. It specifies the relationships between project phases, including transition criteria, feedback mechanisms, milestones, baseline, reviews and deliverables. It addresses the following phases of a S/W project Requirements Phase, design phase, implementation, integration, testing, operations and maintenance.

Below are the common life cycle models

• Waterfall Model
• Prototyping Model
• Rad Model
• Spiral Model
• Component Object Model
• Agile Model

Waterfall Model:
The Waterfall model is an engineering model designed to be applied to the development of the S/W. The idea is the following: there are different stages to the development and the outputs of the first stage "flow" in to the second stage and these outputs "flow" into the third stage and so on.

Prototyping Model:
This is acyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started.Once the prototype is created, it is given to the customer for evaluation.The customer tests the package and gives the feedback to the developer who change the product according to the customer's exact expectation.

RAD Model:
The RAD is alinear sequential S/W development process that emphasizes an extremely short development cycle. The RAD model is a "high speed" adaptation of the linear sequential model in which rapid development is achived by useing a component based construction approach.

Spiral Model:
The Spiral model is the most generic of the models. Most life cycle models can be derived as special cases of the spiral model.It uses a risk management approach to software development.

System Development Life Cycle Model

This is also known as Classic Life Cycle Model or Linear Sequential Model. It has the following activities.

1. System / Information Engineering and Modeling
2. Software Requirements Analysis
3. System Analysis and Design
4. Code Generation
5. Testing
6. Maintenance

System / Information Engineering and Modeling :
This is the initial phase used to understand and indetify the broad project requirements and mail features propsed in the application. In this phase the development team visits the customer and studies their system. They Investigate the need for possible software automation in the given system.

Deliverables for this phase are

•  A rough estimate for effort or price for all phases of the entire project
• A rough schedule for all the phases of the entire project
• An intial function point analysis for all phases of the entire project

Software Requirements Analysis & Specifications:
The objective of the requirements analysis phase is to identify and document the user requirements for a proposed system. The process involves analyst who meet with interview and observe knowledgeable users to understand what the requirements are.

Deliverables for this phase are:

• A final requirements Analysis document delivered for approval.

SystemAnalysis and Design:
The Design phase is the process of designing exactly how the specifications are to be implemented. It defines specifically how the S/W is to be written including an object model with properties and methods for each object, the client / server technology the number of tiers needed for the package architecture and a detailed database design. The logical system of the product is developed in this phase.

Deliverables for this Phase are:

• A final Design Specification. There is no Aproval required for the document. Performance Testing and small prototypes are done to demonstrate technical feasibility.

Code Generation:
 The design must be translated into a machine readable form. The code generation step performs this task. The development phase involves the actual coding of the entire application.

Deliverables for this Phase are:

• A beta version of the application
• Preliminary manuals and user documentaion
• Preliminary as build technical documentation
• A test plan for final product acceptance.

Testing:
Once the code is generated the program testing begins. Different testing methodologies are available to unravel the bugs that were commited during the previous Phases. Different testing tools and methodologies are already available.

Deliverables for this Phase are:

• A final version of the completed application. Other deliverables to complete the development and Test phase are:
• A completed version of the test specification
• Final Manuals and User Documentation
• Final Technical Documentation

Deployment and Maintenance:

The deployment phase is a staged roll out of the new applications.This involves installation and initial training and may involve hardware and network upgrades. S/w will definitely undergo change once it is delivered to the customer. The support phase of the project is the last component and it continues as long as a warranty, extended warranty, or support contract is in place.