Release: 2.1.20
New Features
- Add support for Drone/Harness CI
Bug Fixes
- Railflow exits with successful code even if error happened
Release: 2.1.19
Security Fixes
- Fix security vulnerabilities in axios by upgrading it to the latest version available (1.3.3)
Release: 2.1.18
New Features
- Do not fail the whole build if attachment upload failed
- Add
--no-run
flag to skip run creation in TestRail - Add
--run-id
parameter - Add
--tags-field-name
parameter to store tags from the report file into
Bug Fixes
- Incorrect handling of bulk responses for some endpoints which affects download project functionality
- Fix using milliseconds in elapsed field
- Railflow download project feature: CLI must fetch users for the particular project only
Release: 2.1.17
New Features
- Add support for Playwright reports
- Add a new
JUnit-Steps
report type - Add
--attachment-max-size
switch for limiting attachment size - Add
--attachment-type-whitelist
and--attachment-type-blacklist
switches for limiting attachment types allowed to be uploaded - Improve logging
Bug Fixes
- Duplicate test cases/sections are created when test report contains sections with the same name
- Railflow ignores license file if
RAILFLOW_LICENSE
environment variable is set
Release: 2.1.16
New Features
- Improve parameter logging
Bug Fixes
- "Request body larger than maxBodyLength limit" error on large attachments
- Allure reports: When test case has steps, attachments on test case level are not uploaded into TestRail
Release: 2.1.15
Bug Fixes
- "Incorrect test path. Must start with the name of Master Suite: Master" error while uploading results into baselines
Release: 2.1.14
Bug Fixes
- "No file attached or upload size was exceeded." error happens under some conditions
- Allure: error stack trace is not displayed in TR if error happens outside the test steps
Release: 2.1.13
New Features
- Support for Robot enhanced format
Bug Fixes
- Cucumber: duration of hooks should be added to the duration of the first/last step
- 'npx railflow -v' command does not show the version
Release: 2.1.12
New Features
- Robot: Read test case ID from
testrail.id
tag - Add new RAILFLOW_TR_URL environment variable
Bug Fixes
- Cucumber: Data tables should be displayed in test steps
- Cucumber: "TypeError: The "data" argument must be of type string or an instance.... Received undefined" error
- Cannot set value for custom multiselect field
- When project does not have users and Smart Failure Assignment is set, no warning is displayed
- "error data: Field :custom_required_field is a required field" is displayed instead of a nice validation error message when user provides empty value for a required field
Release: 2.1.11
New Features
- Release for free license model. Support for JUnit reports
- Cucumber reports: Do not create separate steps for before/after hooks
- Cucumber reports: Add ability to map cucumber tests into existing test cases in TestRail by providing the ID in 'testrail.id' cucumber tag
- Allure reports: Add ability to map allure tests into existing test cases in TestRail by providing the ID in 'testrail.id' tag
- Robot reports: Add only fail and warn messages into step's 'Actual' field
Bug Fixes
- Not all warning are displayed in the end of export
- JUnit report: read error and failure from //error/@message element
Release: 2.1.10
New Features
- Set test case title into the field defined by -csf parameter on test case creation
Release: 2.1.9
New Features
- Add new
--untested-status
CLI switch for providing a name of the status to use in TestRail for untested/skipped tests
Release: 2.1.8
Bug Fixes
- Railflow does not create root section if sub-section with the same name exists in some other section
Release: 2.1.7
Maintenance release, no new features/bug fixes
Release: 2.1.6
New Features
- Add support for custom test steps in Railflow Pytest report (https://docs.railflow.io/docs/testing-frameworks/pytest (opens in a new tab))
Bug Fixes
- Duplicate sections are created when search mode is
path
- "Field :parent_id is not a valid section." error in multi-suite project when search mode is
path
- Incorrect handling of Smart Failure Assignment for custom MSTest (TRX) format
Release: 2.1.5
New Features
- Add support for Robot native reports
- Add support for custom Railflow Pytest reports (https://docs.railflow.io/docs/testing-frameworks/pytest (opens in a new tab))
- Add support for SpecFlow NUnit reports
- Add support for customized xUnit reports (https://github.com/railflow/railflow-xunit-examples)(https://github.com/railflow/railflow-mstest-examples (opens in a new tab))
- Add new
--fully-qualified-test-name
CLI which allows exporting fully qualified test names into TestRail - Add automatic retry for failed HTTP requests
Bug Fixes
- Fix an issue with parsing xUnit report generated by xUnit console as they contain some invalid characters
- Railflow creates empty sections when search mode is
name
and all test cases are exists and not located in the section defined by--path
switch
Release: 2.1.4
New Features
- Add new
--upload-mode
CLI switch and do not update the existing test cases in TestRail by default (Railflow just adds a run results for them) - Make test case search case-insensitive
- Add support for enhanced MSTest reports (https://github.com/railflow/railflow-mstest-examples (opens in a new tab))
- Add new
--case-search-field
CLI switch
Bug Fixes
- No error message is displayed for test step Actual field (only stack trace) for TRX reports
npm install railflow
command failed on Node 17 and macOS.
Release: 2.1.3
New Features
- Add support for MSTest/TRX reports
Bug Fixes
- ETIMEDOUT on uploading large report files to TestRail Cloud via proxy server
Release: 2.1.2
New Features
- Add support for enhanced NUnit reports (https://github.com/railflow/nunit_example (opens in a new tab))
- Display missing required parameter names
- Show warning if attachment file is defined in NUnit report but does not exist
Bug Fixes
- ETIMEDOUT on uploading large report files to TestRail Cloud
- Error: Custom case field: 'Steps' ('custom_steps_separated') is required in your TestRail project
Release: 2.1.1
New Features
- Add new --search-mode switch
Bug Fixes
- Do not create section structure for mapped test cases
Release: 2.1.0
New Features
- Add support for Allure reports
- Parallel exporting of results
- Add new --max-concurrent parameter to set the max count of parallel exporting
- Automatic creation of configurations in TestRail
Bug Fixes
- Tests are exported to a wrong sub-section under some circumstances
Release: 2.0
New Features
- Update dependency versions to get rid of various issues
- Node 11 or higher version is required
Bug Fixes
- "Field :results contains one or more invalid results (case C11507 unknown or not part of the test run)" error
Release: 1.9
New Features
- Implement smart caching to reduce number of HTTP requests.
- Add "Smart Failure Assignment" feature
Release: 1.8
New Features
- Add support for the new TestRail API bulk response JSON.
- Handle HTTP 429 "Too many requests" error returned from TestRail server and retry the request after some timeout
Bug Fixes
- Fix the bug in case type handling
Release: 1.7
New Features
- Add possibility to map tests from report files into existing tests in TestRail
- Read license file from http(s)/ftp server
Release: 1.6
New Features
- Adjust logging and write debug logs into file
- Write statistic info into the log file before and after exporting results
- Add new --case-type and --case-priority parameter, allow user to define case properties via the parameter
Release: 1.5
New Features
- Add new --steps-field and --tr-step-results-field parameters
- Show full path to the report file in the error message in case of parsing error
Release: 1.4
New Features
- Automatically identify and upload screenshots in NUnit and Cucumber test reports
Bug Fixes
- Fix the potential problem of using undefined object/variable for cases
- Error on close run attempt
- Fix the bug with failure on empty scenario name in Cucumber
Release: 1.3
New Features
- Support for Cucumber reports
- Add new --tr-template-name parameter to set TestRail template name to be used
- Add new --timeout parameter for connecting with TestRail
Release: 1.2
New Features
- Support for NUnit reports
- Refactor the code of parsing test reports
- Adjust parameter names, order and usage
- Allow users to set custom field labels in case-insensitive way
Bug Fixes
- Configuration names parameter is ignored
Release: 1.1
New Features
- Support for TestNG reports
- Support for JUnit 5
- Show the query URL after uploading
Bug Fixes
- Fix slashes parsing in parameter description
Release: 1.0
New Features
- Automatically parse test reports and export results into TestRail
- Automatically create tests, cases, sections, suites, milestones, test plans, and test runs
- Support for JUnit 4 reports
- All functions are implemented based on the NodeJS, independent of an OS