I'm not sure what you refer to by the "report page". Are you looking at
the navigator.html or the reports.html?
The navigator page is essentially a js page using angular.js to navigate
through the xref.json. You can start from it and modify it to render
the contents of xref.json as you desire.
The reports page is freemarker template but the model is less flexible,
at least in version 3.x. You can remove some information rendered, but
you cannot add things that are not available in the model. From 4.x
you'll be able to have a tree model similar to the navigator at your
disposal to render.
Cheers
On 19/06/2013 11:43, Ritesh Keshri wrote:
Hi,
Thanks for help Mauro. I'm now able to filter Non-implemented
scenarios using meta tag.
In the report page, by default such scenarios are getting captured
under Excluded column of Scenario tab. Can you please suggested some
way to map those scenarios under a customized column "Not implemented"
under scenario tab on report page ?
On Sun, Jun 16, 2013 at 12:59 AM, Mauro Talevi
<[email protected] <mailto:[email protected]>> wrote:
Have a look at tutorial:
https://github.com/jbehave/jbehave-tutorial/tree/master/etsy-selenium/java-spring
Run it and then open target/jbehave/view/navigator.html
It shows how you can filter by meta.
On 15/06/2013 18:37, Ritesh Keshri wrote:
Hi,
Appreciate your prompt response Mauro.
Coming to your question, frankly speaking, I don't have suitable
answer for it, apologies. But, we need it to be implemented for
our project.
As you have suggested to use Mera tags, it really sounds
interesting. I'm newbie to jbehave, It would be a great help if
you provide me code snippet as an example to implement that.
On Sat, Jun 15, 2013 at 8:16 PM, Mauro Talevi
<[email protected] <mailto:[email protected]>>
wrote:
Hi,
may I ask why you feel the need to distinguish between the
two types. It strikes me rather as a sign of
non-collaboration between scenario writers (typically
testers/BAs) and step implementers (typically devs). BDD
tried to foster collaboration and communication.
A pending step is an unimplemented step. The @Pending
annotation was introduced primarily to help prevent the use
of empty method implementations. But an empty method is an
unimplemented method all the same.
If it's the wording that worries you, just rename the keyword
"Pending" to "Not Implemented" and Bob's your uncle ...
Introducing the distinction is JBehave is not trivial, but
while possible we'd still need to convinced of its rationale.
If you prefer, you could use meta tags to mark a scenario as
not implemented, e.g. @status not implemented, but tags do
not apply as step level, only scenario and story.
Cheers
On 15/06/2013 13:58, Ritesh Keshri wrote:
Hi,
Thanks for clarification Mauro.
As per your mail, I understand, JBehave makes no distinction
between those two types of pending steps.
But, as per our requirement, we need to provide distinction
between them . Is it possible to achieve the same?
It would really be a great help if some solution is suggested.
On Fri, Jun 14, 2013 at 1:06 PM, Mauro Talevi
<[email protected]
<mailto:[email protected]>> wrote:
Hi,
pending steps are steps that are either not matched,
i.e. their implementation method is missing, or marked
as @Pending.
JBehave makes no distinction between these two types of
pending steps.
So, your steps in scenario B will be shown as pending as
well.
Cheers
On 14/06/2013 07:32, Ritesh Keshri wrote:
Hi,
Thanks again for response.
As per my understanding if a step is pending DEV team
has to add @Pending annotation in the step class for
that particular step.
My requirement here is- QE team writes a scenario and
but by mistake Dev team did not provide any
implementation at all. I want to capture such scenario
under "Not Implemented" column.
Please find below an example
Scenario A
Step 1 - @pending
Step 2 - @Pending
Scenario B
Step 1 - No Information
Step 2 -No Information
I want to capture scenario B under" Not Implemented"
column in scenario tab of the report.
On Tue, Jun 11, 2013 at 4:20 PM, Mauro Talevi
<[email protected]
<mailto:[email protected]>> wrote:
But that's precisely what "pending" gives you.
It's already provided.
On 11 Jun 2013, at 10:59, Ritesh Keshri
<[email protected]
<mailto:[email protected]>> wrote:
Hi
Thanks for response
I need to add an additional column, "Not
Implemented" in the Scenarios tab. This column
would capture all those scenarios which have been
written by QE but not implemented by Dev
On Sat, Jun 8, 2013 at 1:06 AM, Mauro Talevi
<[email protected]
<mailto:[email protected]>> wrote:
You're going to have to be more specific about
what you're trying to do.
What field are you trying to add? Who
generates the data and when?
Please provide a sample project reproducing
your use case.
Cheers
On 7 Jun 2013, at 13:02, Ritesh Keshri
<[email protected]
<mailto:[email protected]>> wrote:
Hello,
I have a requirement to add a new field in
jbehave report page. Can you please let me
know how to customize jbehave report page.
Below is the sample what I want to achieve in
report page :
___________________________________________________________________
Steps
____________________________________________________________________
Total | Successful | Pending | Failed | No
performed | *customized_filed* | Ignorable
_____________________________________________________________________
--
Regards
Ritesh
+91-9535084967 | Bangalore | India
--
Regards
Ritesh
--
Regards
Ritesh
--
Regards
Ritesh
--
Regards
Ritesh
--
Regards
Ritesh
