Have started using cucumber framework for testing of my project.
Able to generate cucumber html , json and xml report.
I am looking for something like JIRA ID link to be represented against feature representation in report.
Can anyone help me in this.
In the past, I have used tags to represent JIRA tickets in scenarios/features. For example, if you have a JIRA ticket with ID JIRA-123, your scenario could look like this:
#JIRA-123
Scenario: ...
You should then be able to see from the cucumber reports which features/scenarios are marked with which tags. You can build a custom report that fetches all the JIRA tags and retrieves ticket information from JIRA in runtime using for example JS and the JIRA API.
A major flaw in what you are trying to do is that Jira tickets are historical whilst scenarios are current.
Jira tickets document what was being done at a particular time in the projects lifecyle whilst scenarios document the current state of the application.
Scenarios have current knowledge of the application. Jira tickets only have the knowledge that was available when they were created.
Trying to link these two very different things has some negative consequences including:
You stop people from refactoring scenarios to reflect the current state of the application, because they need to maintain the links with the jira history.
Your links mislead, a scenario changes over time to reflect the current application but your links imply that what is in the jira ticket still applies.
Link management becomes very confusing, scenarios end up with multiple links and links get removed or applied to un-related scenarios as refactoring takes place.
Point 1 is particularly important. Scenarios can very easily become slow, unreliable and unwieldy. They can significantly increase the cost of change for an application unless they are very well managed. Anything that stops this management is detrimental.
Related
We're starting a new development project using on-premise TFS 2018, git and Visual Studio. In the past we've followed the Agile model of creating epics and user stories and putting the requirements/ui mockups and other details directly in the user stories.
After living through that approach, we don't want go back down that road for the following reasons:
1) Once that feature is shipped, it becomes extremely difficult to locate the info. Who remembers what feature was done in what user story?
2) No centralized place to store feature documentation. Of course, we all don't want take the waterfall approach of spending 2 years writing feature requirements, but there is something to be said of having a centralized place organized by feature area that contains the relevant documentation.
3) Have you ever tried to read an extensive user story with requirements acceptance testing through either the web interface or through Visual Studio? It gets old pretty fast having to read through a 8 line window.
What we would like to do is do a hybrid of documentation and reference a link to the doc in the user story. The user story exists for sprint tracking, but the details are stored in the document. After the feature/user story has shipped, we can refer to the doc.
Therefore the question becomes how to store this type of info in TFS and link to it so it can open with a link in the user story. We know we can do this with SharePoint, but is it possible to do in on-premise TFS?
Currently, this is not directly possible in TFS with outgoing with some 3rd party vendors like Modernrequirements which will be paid services.
You could always use the CMMI template which is used for creating and managing requirement Workitems, but not for storing a huge set of requirements as you typically stored in requirement documents.
As you mentioned there are other ways like Storing the documents in
SharePoint, one drive etc., and link to the user stories
Creating a
markdown
in the user stories itself.
Check-in those documents in the version control(Git,TFVS)
Refer to this similar SO in order to understand it better.
I am trying to use "Flow" to automate emails every time a new item is added to a SharePoint discussion board.
This is working fine with all lists, however, it does not do anything when I create a flow for the discussion board. The name of the discussion board does not even come up as an option in the "List" category and if I use the "Documents" option instead of the lists, I am able to choose the correct discussion board, but the alerts do not work.
Discussions are based on the folder content type, with each reply to a parent discussion being an item within that folder.
Flow does not currently support many triggers or operations against folders (including discussion boards) in SharePoint sites, though they've been steadily adding functionality since Flow was introduced.
It's possible that this functionality will be added in the future. You can make suggestions and vote on proposed functionality in Microsoft's "Flow Ideas" community.
A bit of background before I begin.
Background:
I am working on migrating an existing .NET based system to Dynamics CRM and one of its key feature is its 'Request Approval Process'. I have implemented some simpler versions of such approval processes in past but this one is a bit complex since it involves multi-level approvals, multiple approvers at one level, amendment logic, delegation functionality, etc.
Analysis Till Now:
Before pushing this question at SO, I did a fair analysis of the requirements from my end and have come up with few possible approaches:
Workflow based approach (something on lines of this)
Complete custom logic using Plugins/Web Resources (something on lines of this)
I am not explaining the details of these approaches as of now but the core issue is that none of these two approaches are fitting correctly to my requirements.
Queries:
While analyzing these approaches I came across some newer functionalities added to CRM (listed below) but did not get any additional resources to explore them further. I just want to confirm that I am not trying to achieve something which is already present out-of-the-box or going in the incorrect direction.
1. Internal Process Automation:
Reference: Here
Any leads/thoughts on this approach? I am not able to find any good documentation/articles around this.
2. Graphical Approval Workflow:
Reference: Here
This feature seems to be useful but it is mentioned to be a part of Dynamics Marketing. With the new structuring of Dynamics 365, will this feature be a part of Dynamics CRM by default?
Also, the Prerequisites section of this link mentions certain Item Types for which you can configure this functionality. So can't we use this functionality for any entity records?
Any kind of help/inputs would be appreciated.
I'd suggest the best of both worlds: using out-of-box Workflows along with custom Workflow activities that you can write with C#. Use as much out-of-box functionality as you can, but when you need to query records or run custom logic, create a custom workflow activity that can be used in your out-of-box Workflow. Custom workflow activities are similar to plugins in that they are written using C#. You can have custom inputs and custom outputs for your activity.
For example, maybe your approval process needs to look up the appropriate approving user for this record. You could write a custom workflow activity that takes an input (the record being approved) and an output (the user that has the ability to approve). Then in your Workflow, you'd add your custom activity as a step. After that step, you could send an email to the approver by using the output of that custom step.
More information about custom workflow activities: https://msdn.microsoft.com/en-us/library/gg309745.aspx
I'm looking into upgrading a .net 2.0 app. The app is used by the public authorities of a certain city to keep track of expenses and generate reports and forms.
The reports and forms were generated in VS2005 using Crystal report. They follow a well defined layout, like official documents usually do.
I am looking at options to upgrade the application and the main problem I have is in determining how to deal with the crystal report files.
I have successfully upgraded to VS2008, but any version after that doesn't have CR anymore, so my company would have to pruchase CR separately and because the client and my company are both tight, I'm looking at alternatives...
The obvious one is using SSRS. I have never touched it before in my life, but after playing around with it for a bit, I get the impression that it is not very well suited to generating forms with lots of non-tabular content and lots of formatting. Or am I wrong?
It seems that every line has to be drawn separately. There is no (that I can see) accurate way of positioning lines for formatting...
But I'm just a beginner, so I might be getting this all wrong?
If that is the case, are there any other alternatives to CR and SSRS?
I was thinking of maybe having a separate MVC web site project in the solution. Have that generate the layout in html and css with data from my entity model, then view the result in a (built-in or not) web browser. Am I overcomplicating on this?
I really need advice from somebody who's done that kind of thing before.
What SSRS is good for:
Talking to SQL Server, much faster than other products as it in many cases retains the database better when in other programs IMHO they repeat query at times.
Designing collapsable grids and chart objects from datasets. You can have 'groups' that can nest aggregates of collapsed values and can be un collapsed or collapsed on demand based on expressions, parameters, or a recusive parent set.
A web service for deployment ease where you can deploy one or many objects. You can also write add ons for this service with C# and the ReportingService.asmx web service.
You can talk to the web service directly in a 'form' object in HTML and manipulate it's output.
You can schedule reports to send out via email and file saves automatically to clients or internal users.
What SSRS IS NOT GOOD FOR:
It is not event driven hardly at all except for parameters. You cannot click on many things and get other parts on the form itself to update. You may do an 'action' that goes to another location, report, or site. But in essence you are calling a seperate object, not the same instance again.
Multiple layers of reporting. Beyond tweaking tool tips you cannot do 'hover over' reporting without hacking SSRS. You can make javascript windows show other reports but it is not baked in to SSRS. So you are either clicking into new reports or tab stops in a report but not getting hover over quick objects beyond text and expressions that are in tool tips.
What do you want before considering what you need to impement?
I want to input and export things while talking to my database - ASP.NET with potentially HTML 5 or MVC4 if you want to be very new. ASP.NET is made for actively talking to a server and taking commands IN as well as OUT.
I want a form to auto update periodically on a page as a landing site and dashboard - AJAX and Javascript on top of HTML, Java or ASP.NET.
I want to create reports that exist on a Server and can be hosted on a wide variety of platforms in .NET via web service calls - SSRS.
SSRS's biggest selling point to me is it's reusability once you dial a report in. They are pretty easy to create, easy to configure, easy to deploy, and if you get a little advanced in calling the webservice you can get SSRS report objects in other technologies if you want.
There is Crystal reports for VS2010 and VS2012. It is just not shipped with them. You can download the installation from here: http://scn.sap.com/docs/DOC-7824
I am running through the same decision process at this time. There is a .NET product from a company called "Windward" that will allow you to design your reports in Microsoft Office. If you are in the MS ecosystem already or want your users to design reports instead of always calling on you, this might help.
Their template design tool is called AutoTag and you can deploy these template to their .NET based engine in a few lines of code.
I know the question is regarding SSRS vs. Crystal comparison but thought you should know there are other alternatives and some can make life easier
Ryan
I would like to include release notes with every release of our intranet project. We use Jira. Is there a way to generate the release notes automatically based on the fixes that were submitted to SVN? We usually check the files back with the jira key id.
vikasde,
To my knowledge Jira does not offer a way to retrieve this information in a straight-forward manner on a jira number basis. However, it has been quite some time since I looked into this. Jira does generate release notes for all jiras contained within a release (fixes checked in or not). What I have done in the past, as part of the release build, is to have a script retrieve the contents of the "Edit/Copy Release Notes" jira url and paste that into an xml file stored within the build products. If there is a better way to achieve this functionality I would definitely be interested as well.
EDIT: It appears that starting in Jira 3.5 you can retrieve issues by id through the soap interface.