Re: [QF-Test] QFS Framework required

• Subject: Re: [QF-Test] QFS Framework required
• From: Karlheinz Kellerer <Karlheinz.Kellerer@?.de>
• Date: Mon, 10 Jun 2013 08:40:32 +0200

Hi Mohammadyaseen,

There is no option in QF-Test to restrict functionality the way you
requested.

Indeed I think having an expert team providing a proper set of
reusable procedures is very important and efficient.

But limiting end users to just those procedures will lead to quickly
blocking them in all situations where no 100% fitting procedure is
available and it will be hardly possible to provide all relevant
procedures. This deadlocks and need to for too many specific
procedures will result in overhead, delays and frustration for both the
end users and the expert team.

I recommend to install guidelines how users shall effectively build up
their test-suites by use of given library procedures and why they
should avoid too much specific code. Also define a way how to feed back
generic parts to the expert team to transform those into library procedures.

A review process might help to ensure quality of test-suites.

If necessary, you could install some kind of automatic sanity check,
e.g. by parsing QF-Test XML test-suites and warn if certain metrics
are not met.

I also recommend to have a look at

http://www.qfs.de/qftest/manual/en/bp_organize.html#sec_bpOrganize

which contains helpful hints on test-suite organization.

Hope this helps.

Best regards,
    Karl

"Walikar, Mohammadyaseen (NSN - IN/Bangalore)"
<mohammadyaseen.walikar@?.com> writes:

> Hello,
>
> In continuation of discussion as Gokul had with you, we wanted to check how best we can develop
> the framework tool available in QFS.
>
> We have identified, few key users who will develop Procedures and want to re-use only these
> Procedures and Automate the test cases.
>
> Is there anyway how we can control these, so that all the other users can call Only the procedures
> which are written by key users and not to record every time.
>
> One option we thought was disabling all other OPTIONS except “Procedure Nodes” (as marked in
> picture below). If this works for us, please suggest how to disable these options.
>
> [cid]
>
> With regards
>
> Yaseen Walikar
>
> From: Prakash, Gokul (NSN - IN/Bangalore)
> Sent: Wednesday, June 05, 2013 10:14 PM
> To: Walikar, Mohammadyaseen (NSN - IN/Bangalore); Venkat, Murali (NSN - IN/Bangalore); Dnv,
> Hanuman (NSN - IN/Bangalore)
> Subject: FW: [QF-Test] QFS Framework required
>
> Fyi
>
> Sent from my Windows Phone
>
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>
> From: ext Gregor Schmid
> Sent: 05/06/2013 20:22
> To: qftest-list@?.de
> Cc: Prakash, Gokul (NSN - IN/Bangalore)
> Subject: Re: [QF-Test] QFS Framework required
>
> Hello Gokul,
>
> data driven testing is supported directly by QF-Test as explained in
> manual chapter 14:
>
> http://www.qfs.de/qftest/manual/en/user_datadriver.html#usec_datadriver
>
> Whether you want to use additional test management or test execution
> or continuous integration frameworks is up to you and your company's
> policies.
>
> For a list of tools for which an explicit integration exists, please
> see manual chapters 19 and 20:
>
> http://www.qfs.de/qftest/manual/en/user_testmanagement.html#usec_testmanagement
>
> http://www.qfs.de/qftest/manual/en/buildtools.html#usec_buildtools
>
> Best regards,
>     Greg
>
> "Prakash, Gokul (NSN - IN/Bangalore)" <gokul.prakash@?.com> writes:
>
>> Agreed Greg. Thanks for the detailed explanation w.r.t Framework query.
>>
>> What's your best proposal to use framework for QFS tool? Do you have any framework tool
> available in QFS ?
>>
>> My intention is to automate our product test cases via SUT as part of data driven concept ?
>> Do you see any possibility here or can u throw some light here ?
>>
>> Regards,
>>
>> Gokul Prakash T
>>
>> -----Original Message-----
>> From: ext Gregor Schmid [mailto:Gregor.Schmid@?.de]
>> Sent: Tuesday, June 04, 2013 11:22 AM
>> To: qftest-list@?.de
>> Cc: Prakash, Gokul (NSN - IN/Bangalore)
>> Subject: Re: [QF-Test] QFS Framework required
>>
>> Hello Gokul,
>>
>> QF-Test is geared towards GUI test automation, it doesn't try to
>> replace test management or test execution frameworks, but rather to
>> integrate with those.
>>
>> I don't know of any existing integration of QF-Test with STAF/STAX,
>> which is indeed a very powerful framework for distributed execution,
>> but if you've got STAF set up, QF-Test is just another tool to
>> call which is not a problem, thanks to its command line interface for
>> batch mode.
>>
>> One thing to look out for on Windows is how to run the STAFProc
>> service so that the SUT can run in a real user session. This is
>> similar to the problems faced with Hudson/Jenkins and other build and
>> execution tools. Further explanations are provided in our FAQ #14:
>>
>> http://www.qfs.de/qftest/manual/en/faq.html#faq_14
>>
>> Best regards,
>>     Greg
>>
>> "Prakash, Gokul (NSN - IN/Bangalore)" <gokul.prakash@?.com> writes:
>>
>>> Dear Servicedesk,
>>>
>>>    Since we are registered and purchased QFS tool for our product automation. I would like to
>>> know, do you have any Framework Tool in your organization.
>>>
>>> As you all know, STAF (Software Test Automation Framework runs on QTP, WR etc tool). Do you
> have
>>> similar framework or not ?
>>>
>>> .STAF is an automation framework intended to make it easier to create and manage automated
>>> testcases and test environments.
>>>
>>> .STAF is supported on Windows, Linux, Mac OS X, AIX, Solaris, HP-UX, z/OS, IBM i, FreeBSD
>>>
>>> .STAF externalizes its capabilities through services. A service provides a focused set of
>>> functionality, such as Logging, Process Invocation, File Manipulation, Resource Pools,
> Semaphores,
>>> Events, etc.
>>>
>>> .STAFProc is the process that runs on a machine, called a STAF Client, which accepts requests
> and
>>> routes them to the appropriate service. These requests may come from the local machine or from
>>> another STAF Client on a remote machine. Thus, STAF works in a peer environment.
>>>
>>> .STAX is an execution engine for STAF which can help you thoroughly automate the distribution,
>>> execution, and results analysis of your testcases.
>>>
>>> .STAX provides support for parallel execution, user-defined granularity of execution control,
>>> support for nested testcases, the ability to control the length of execution time, and the
> ability
>>> to monitor STAX jobs.
>>>
>>> Regards,
>>>
>>>
> ---------------------------------------------------------------------------------------------------------------------
>>>
>>> Gokul Prakash T | Nokia Siemens Networks Private Limited
>>>
>>> Maintenance @Com for Core
>>> L5 - 4th Floor, Manyata Embassy Business Park,
>>>
>>> Nagavara,Bangalore 560 045
>>>
>>> Extn: 6411 | Tel:+918043636411
>>>
>>> Mobile: +919731397000 | E-mail:gokul.prakash@?.com
>>>
>>> https://twiki.inside.nokiasiemensnetworks.com/bin/view/Main/BSOSOMTSPSOSSAdvantageCommander
>>>
>>>
> ---------------------------------------------------------------------------------------------------------------------

--
Karlheinz Kellerer                     Karlheinz.Kellerer@?.de
Quality First Software GmbH                    http://www.qfs.de
Tulpenstr. 41                              Tel: +49 8171 3864813
DE-82538 Geretsried                        Fax: +49 8171 3864816
GF: Gregor Schmid, Karlheinz Kellerer         HRB München 140833

• References:
  • [QF-Test] QFS Framework required
    • From: Prakash, Gokul (NSN - IN/Bangalore)
  • Re: [QF-Test] QFS Framework required
    • From: Gregor Schmid
  • Re: [QF-Test] QFS Framework required
    • From: Prakash, Gokul (NSN - IN/Bangalore)
  • Re: [QF-Test] QFS Framework required
    • From: Gregor Schmid
  • Re: [QF-Test] QFS Framework required
    • From: Walikar, Mohammadyaseen (NSN - IN/Bangalore)

• Prev by Date: Re: [QF-Test] QFS Framework required
• Next by Date: [QF-Test] Check the state of the checkbox of a tree node
• Previous by thread: Re: [QF-Test] QFS Framework required
• Next by thread: [QF-Test] Different JDialogs with the same title, different components?
• Index(es):
  • Date
  • Thread