One way to 'migrate' is to just use the R&P to record small 'blocks' of interactions and then call these interaction blocks, stick them in separate methods in a library then call them from a test in sequence.
After this you could paramatise the details of the the block or modify each block to pass n data from the test so that it can be used in more than one instance. E.g. pass in the web page address to a generic 'goto web page' block.
Then put the steps into a spreadsheet and data drive the sequence from there. as per the fine videos on this site.
You can only keyword/data driven tests when you have done the underlying code blocks that make up a full test. This is all up front work that pays back later down the line.
After this you could paramatise the details of the the block or modify each block to pass n data from the test so that it can be used in more than one instance. E.g. pass in the web page address to a generic 'goto web page' block.
Then put the steps into a spreadsheet and data drive the sequence from there. as per the fine videos on this site.
You can only keyword/data driven tests when you have done the underlying code blocks that make up a full test. This is all up front work that pays back later down the line.