Topic: Functional Testing

Message

   Functional Testing
The objective of this test is to ensure that each element
of the application meets the functional requirements of the business as
outlined in the :

Requirements Catalogue

Business Design Specification

Year 2000 Development Standards

Other functional documents produced during the course of
the project i.e. resolution to issues/change requests/feedback.
This stage will also include Validation Testing -
which is intensive testing of the new Front end fields and screens. Windows
GUI Standards; valid, invalid and limit data input; screen & field
look and appearance, and overall consistency with the rest of the application.

The third stage includes Specific Functional testing
- these are low-level tests which aim to test the individual processes
and data flows.

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: Functional Testing Posted: 29Oct2007 at 4:25am
	Functional Testing The objective of this test is to ensure that each element of the application meets the functional requirements of the business as outlined in the : Requirements Catalogue Business Design Specification Year 2000 Development Standards Other functional documents produced during the course of the project i.e. resolution to issues/change requests/feedback. This stage will also include Validation Testing - which is intensive testing of the new Front end fields and screens. Windows GUI Standards; valid, invalid and limit data input; screen & field look and appearance, and overall consistency with the rest of the application. The third stage includes Specific Functional testing - these are low-level tests which aim to test the individual processes and data flows. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged

ksrikanthinbox Newbie Joined: 05Oct2007 Location: India Online Status: Offline Posts: 1	Posted: 26Dec2007 at 7:21am
	Functional:Checking the behavioral of functional reaquirements of application. 1.Behavioral coverage/Gui coverage 2.Error handling Coverage 3.input doamin coverage 4.manipulations coverage 5.Backend coverage 6.Functionality order coverage Gui Coverage:In this coverage testengineer obserevs the behaviour of objects in screens of product with respect to corresponding functionality and validate changes in properties values of objectx. Error handling coverage:In this coverage testengineer obserevs the behaviour of objects wiht respect of invalid events Input domain coverage:Test Engineers go to special treatment to input domain testing in terms of boundary value analysys(BVA),Equliance partiniong(EQA)on range or size of input object. manipulations coverage:In this coverage testengineers validate output or outcome of that corresponding functionality at the end. Backend coverage:In this coverage testengineers validate the impact of Front-end functionality on the backend databases tables in terms of data validatin and data integrity. Functional order coverage:In this coverage test engineers find place of testing functionality in that product.
	IP Logged

Georgiodz Newbie Joined: 30Jan2009 Online Status: Offline Posts: 1	Posted: 20May2009 at 4:15am
	Overview of approaches for functional web testing: functional web testing software Edited by Georgiodz - 05Jun2009 at 6:03am
	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Functional Testing @ OneStopTesting