-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for xls files #147
Comments
It might be possible. Can you say more about how you would like this to
work?
…On 2017-03-10 07:48, Valeri Vicneanschi wrote:
Is is possible to add support for xls files like in FolderRunner?
http://butunclebob.com/FitNesse.UserGuide.FitLibraryUserGuide.FolderRunner
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#147>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACXY-R8oRDIj1h9PIuImHh97kxhVECsks5rkWLYgaJpZM4MZd7U>.
|
Basically it should read Excel Spreadsheet instead of HTML. I found the Java sources for fitlibrary which supports SpreadsheetRunner:
There are some examples of xls files here:
It's more convenient to work with Excel files because you can use formulas. |
Thanks. I'm taking a look at it. These are old style Excel files
(.xls), I assume we'd use current style (.xlsx) now.
…On 2017-03-14 12:01, Valeri Vicneanschi wrote:
Basically it should read Excel Spreadsheet instead of HTML.
I found the Java sources for fitlibrary which supports
*SpreadsheetRunner*:
* (git) https://git.code.sf.net/p/fitlibrary/fitlibrary
(src/fitlibrary/runner/SpreadsheetRunner.java)
* (zip)
https://sourceforge.net/projects/fitlibrary/files/FitLibrary%20in%20Java/FitLibrary-2.0.zip/download
There are some examples of xls files here:
* https://git.code.sf.net/p/fitlibrary/fitlibrary/folderRunner/tests/trySetUpTearDown/SetUp.xls
* https://git.code.sf.net/p/fitlibrary/fitlibrary/folderRunner/tests/trySetUpTearDown/testConnectAndDisconnect2.xls
* https://git.code.sf.net/p/fitlibrary/fitlibrary/folderRunner/tests/trySetUpTearDown/TearDown.xls
It's more convenient to work with Excel files because you can use
formulas.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#147 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACXY00b3UXggoBgAusZI-Fj1N37jG9kks5rltX_gaJpZM4MZd7U>.
|
I agree about .xlsx |
looks reasonable to do. I'll add it to next release (no target date yet) |
Thanks Mike!
On Tue, Mar 21, 2017, 11:40 AM Mike Stockdale ***@***.***> wrote:
looks reasonable to do. I'll add it to next release (no target date yet)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#147 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACv_1Bv0abnSfMfzjxEhttoDGn8Cc5CPks5rn-93gaJpZM4MZd7U>
.
--
Best regards,
Valeri Vicneanschi
|
I would love this feature. We define alle our tests in Excel and paste them into Fitnesse manually. It is tediuos work when we make changes that require recalculation of answers. It would be great if we could run the tests directly from xlsx files! |
Early release 2.6.1 has a preliminary version of this feature |
We are using the SLIM test system to run our test (fitSharp.Slim.Service.Runner). As far as I can understand, the SpreadsheetFormat support added now only works using FIT? Is it possible to use this new SpreadsheetFormat feature within a test suite already containing test in the SLIM test system? Ideally, I would like it to be possible to have folders with .xlsx and .xlsm files which are automatically parsed and executed along with our existing files (which is currently defined in "content.txt" and *.wiki files). |
Spreadsheets are not supported for SLIM. I can't control the SLIM file formats from fitSharp. You could request spreadsheet support for SLIM here: https://github.com/unclebob/fitnesse/issues |
Is is possible to add support for xls files like in FolderRunner?
http://butunclebob.com/FitNesse.UserGuide.FitLibraryUserGuide.FolderRunner
The text was updated successfully, but these errors were encountered: