Printable View
Hi All,
Please help me in finding out a answer to the below mentioned question:
1) Functional Test cases are written from a) User perspective
a) User perspective
b) Design Perspective
c) Client Perspective
d) Developer Perspective
2) How do you calculate the effort for Re-testing?
a) Interacting with developers.
b) Time calculated for Regression Testing.
c) Metrics from similar project.
Thanx n regards,
balaji
Functional testing is concerned about external behaviour of software e.g. input is properly accepted, output is correctly produced and integrity of external information is maintained. Test cases are based on high level description of software requirement. In this approach of testing, tester sees application as a black box means tester is unawared and unconcerned about internal structure of program.
well, what u explained is quite usefull.
but plz explain about retestig and it's terms and conditions.
Hi
Functional Testing includes the functionality of testing where we do testing 80% in system testing
in this we write test cases based on 3 scenarios
1.Businees Test case -80%
2.Input Domain test case -15%
3.User Interface test cases 4%
4.Gui based (if required )- 1%
1.Business test case
We should study the use case of functional specs
and
1.we should identify the entry condition what the functionality can be done on
2.the exit criteria (example :Like Logout)
3.find the alterantive condition if any for that.
4.the stop criteria.
repeat this criterias on use case of functional specs
and start writing the cases as for business test case
2.Input domain
read attributes
find critical among them
and create data matrix for them
3.user interface
alignment,font..etc
4.gui based
optional...
Retesting :- Doing testing the application with different types of data
and also passing the number of parameters for the application
ex:- datadriven test
[QUOTE=testingjob_vb;3026]Hi All,
Please help me in finding out a answer to the below mentioned question:
1) Functional Test cases are written from a) User perspective
a) User perspective
b) Design Perspective
c) Client Perspective
d) Developer Perspective
2) How do you calculate the effort for Re-testing?
a) Interacting with developers.
b) Time calculated for Regression Testing.
c) Metrics from similar project.
Thanx n regards,
balaji[/QUOTE]
hi balaji
i think people tried to a lot to answer your questions but in vain....
answer to the first question is d) developers perspective as functional testing is done to find the problem with the system if there is any..however we can insert business scenarios in our test wares.....it is more inclined towards the finctionality of the system......now whether the system has met business requirements or not would be checked under UAT...
and answer to the second question depends upon that at what stage of the testing life cycle the effort estimation is being carried out...
usually we consider it at the time of putting our proposal writing
and at that time it may be difficult for the person who is estimating to know about the regression schedules and discussion with the developers...so metrics from the past similar projects can work as a boon at that time
hope that solves your problem...
Functional testing is done according to Design and regression testing done when we have made any enhancement or fixed any bug.