Reuse recipe in google dataprep - google-cloud-dataprep

I am trying to use existing recipe from one dataset to another. Unfortunately, i am unable to locate the steps by steps process in the google cloud documentation.
Could someone assist with the steps?
Thank you!

There are some ways you can do that. For example, if you want to keep your recipe/dataset combinations in separate flows, you could make a copy of the flow (there's an option in its menu), go into the flow, choose "Replace" from the menu of the dataset linked to the recipe you want to reuse and give your new dataset as input. If, on the other hand, you'd rather keep everything together in the same flow, you could go into that flow and choose to make a copy of the recipe you want to reuse. Then, from that copy's menu, choose "Change input".

Related

How to import test cases from Excel to VSTS/Azure DevOps

I have a lot of test cases which are currently in Excel that I need to migrate those to VSTS/Azure DevOps. Can someone recommend me a good way to do that.
This is a manual way but maybe it will be useful for you.
On IE or Edge. You can try the grid view on your test plan and just copy/past test cases:
In test suite select creation of test cases with grid view:
Copy/past you test cases and save edits:
Install Team Foundation Server Office® Integration (Excel Add-In)
Open Excel and go to Team Tab and then click on New List
Connect to your TFS
Choose Input List then click OK
Click on choose columns so we get all the necessary ones for creating test cases
The Work Item item is set to "All Work Item Types", change this to "Test Case"
Click Add Required and you should have about 8 columns, then click ok
Now you should see a slightly different excel worksheet. -Change the work item type on the first line to "Test Case" and it should auto-populate the defaults
I searched for almost an entire week before getting this to work and there were no answers online so, I thought I would share.
Install the Test & Feedback plugin for Chrome. (*this may or may not be necessary but it worked for me and I have this installed)
Navigate to the *old view of the Test Plan.
Note: To confirm you are in the 'old view', a blue link in the upper right hand side that says 'Switch to new view' will be displayed.
Note: When you hover over the test icon in the left navigation bar, choose the option "Test Plans" not "Test Plans*". The latter is the new view.
Select the folder that contains the test cases on the left and wait for the Test Cases to populate in the pane on the right side.
Click "Offline Test Execution" at the top of the pane above the Test Cases.
Choose to export the entire Test Plan or entire suite of Test Cases, etc., and click 'Export'.
Note: If you try to export the entire plan or several folders worth of test cases and the export fails, choose less test cases at a time to export.
Hope this helps.
I was able to upload the test cases including the test steps using Microsoft Test Manager and which can be accessed through Azure devops.
If you guys have Microsoft Test Manager, please find the required information at the below link.
https://github.com/premboyapati/Test-Case-Migrator-Plus

Extend local history to save more data on changes

We are evaluating a project where eclipse should be extended in a way to enable more analysis on code changes. As these changes are already stored by eclipse in the local history, we don't want to save all data again in files on the system and are searching for a good way to efficiently build it on top.
More details:
Java files are changing multiple times in a lifecycle of a project. To build some statistics about developer habits, we want to store additional data as last time modified, username, some user input, and some more things. This data should be displayed in a compare view with annotations but should be a normal comparison view also.
We don't find any extension points or classes to extend, which could make this possible so we think asking here for help is maybe a try to find an answer/tip for our project.
Thanks to all in advance.

How to export bug list (or any custom query) from TFS to Excel from a command line?

I need to export list of bugs from our Team Foundation Server to Excel. It's trivial to do it manually, but I need a command line version since the task needs to be automated.
Anyone knows how to do this?
To answer your origional question:
Add a new query in TFS, create your query and click save. This should give you an option to save the query either on the sever or locally. If you chose to save it locally and then change the extension from WIQL to .txt you will have the query available to you :-)
I hope you are aware that you have the option of using the 'Team' tag in your Excel/Project ribbon. Having said that, you can create a macro in excel that consumes the refresh or publish button on the team ribbon. Have a look at this sample macro http://blogs.msdn.com/b/teams_wit_tools/archive/2007/03/15/how-to-invoke-tfs-add-in-controls-from-macro-code.aspx
HTH.
Cheers, Tarun

Writing a macro-like tool

Recently I've been finding myself doing repetitive tasks. I would click button A, highlight text field A, type in some text, click an APPLY button, click on a drop-down box and select a specific option depending on the item I'm working with, select it and hit APPLY, then repeat this process only a couple hundred to thousand times.
So I thought maybe there's a way I could automate this? Macros then came to mind. However I've never wrote macros before so am not sure of several details such as
-what tools should I even work with?
-how do I determine which button to click?
-ideally, I would want to be able to read input from a text file to specify what should be typed in and which option should be selected from the dropdown list. Is this even possible? It seems like an operation that require some intelligence.
I am not picky on tools nor about cleanliness. I just want to be able to automate the process. It will be for personal use unless I find a convenient way such that others can use it as well.
Some details about the dropdown box: when the box is focused, I can hit the DOWN key to scroll from option to option. The items that I have to associate with these options are named exactly the same, so they appear in the same "index" order (meaning, the first item and first option appear at the top of the list, second item and second option appear after, thid item and third option...etc)
The placement of all of these fields can be fixed, so if I have to manually specify where on the screen I should be clicking, that is also a possibility.
Any idea where I should look?
If you're using Windows, AutoIt is a really nice tool.
It records actions (like a word/excel macro)
It offers a BASIC like language + API which is really easy to program (if you need to)
The API is pretty powerful
Check for Windows with a certain title
Automate klicks
...
You can "compile" your scripts into exe files so you can share your tools
It comes bundled with Scite (a nice text editor) + AutoIt syntax higlighting
But you can use any editor you want
It's well documented
It's Freeware
http://www.autoitscript.com/site/
On the Mac, there is Automator. Java has the Robot class in the basic library, to help with such automation. No doubt there are other similar tools.

PowerBuilder IDE Customization for SCC

Our PowerBuilder application is fairly large and has many objects in several PBLs for organizing our code. We often have 10 or more datawindows on one window, and these datawindows may be spread across two or three PBLs. For version control, we use exclusive check-out to avoid merge conflicts.
The situation is that when you right-click on a datawindow object from the Window painter you get a context-menu with options like "Script" and "Properties" and "Modify Datawindow...". We'd like to add one for "Check-out..." to avoid having to hunt for the datawindow in several PBLs.
Any ideas on how to do this, or something similar, would be greatly appreciated.
I think the best you can do is to create a temporary library at the top of your library list, locate your datawindows by jumping to them via "Modify Datawindow...", then saving them into your temporary library, and finally using the tools in your source control system to locate them by name and lock them.
One other trick that I use is to uncheck the tick box in the source control options that clears down the .srd etc files, then using your operating system's find tools to search on file name for these (since Powerbuilder still doesn't support searching for objects by name...). Of course if you don't have many objects, and if your objects don't have many references, you could always use Powerbuilder's search... but who do you know in the that fortunate position?!!
I think you've hit on a problem that a lot of people run into, which runs right through a loophole in PB that lets you start editing a DataWindow without warning you to check it out. Unfortunately, to the best of my knowledge there is no way to hook into the context menu.
However, you can hook into toolbar items. If that was the way I wanted to go, and I had plenty of time to spare, I'd write an app that I would launch from the toolbar, and here's what it would do:
Find the PowerBuilder window with APIs
Find the current sheet in PB
Get the object name out of the title
Get the current application (registry or PB.INI, depending on the version of PB, and may involve getting the workspace first, then the current target)
Get the library list (PB.INI or target file)
Do a LibraryExport() on the object that's open
Find all DataWindow controls (this may involve looking at ancestors to determine control types)
Identify dataobjects for these controls (again, you may need to look at ancestors)
Use LibraryDirectory() to get a list of all objects in all PBLs
Find the dataobjects' PBLs
Throw up a window listing the dataobjects and their PBLs
OTOH, if I had PBL Peeper (and, yes, this is biased advice), I'd
Launch the "PBL Peeper (Browse current application)" icon on my desktop (OK, that's a lie; I'd already have PBL Peeper open and would just switch to the Browse page)
Ctrl-Q (for QuickFind) and start typing the name of the object (if you pause, it will find a partial match on what you've typed)
Hit [Enter] once to accept QuickFind's selection
Hit [Enter] again to expand the object
Find the DataWindow control in question and RMB on it
Select "Go to Default DataWindow"
If it doesn't show the library and name in the microhelp (it's been a long time since I've released a version, and I can't keep track of what's in the released version), find the Up toolbar item to go up to the PBL
I know this doesn't achieve a checkout, but it does "avoid having to hunt for the datawindow in several PBLs". And, you can probably achieve this faster than my first suggestion.
Good luck,
Terry
The way I do it is to right-click and choose Modify DataWindow. When the painter opens you can just read the PBL from the title of the painter. Then close the DataWindow painter so PB will let you check out the DataWindow. For the more general case of locating an arbitrary user object, use Terry's PBL Peeper method.
You could separate the organization of PBLs used for development from those used for deployment.
As long as the PBL names don't conflict between the two views into the source code. The PBG files registered in source control won't clobber each other.
The downside is that when new objects are added or deleted, you will need to update both locations.
I would create a datawindow only PBL with all the related objects and put them in the same target. When I worked with that sub-system or report i could then check out all the objects in the same library.