-
Notifications
You must be signed in to change notification settings - Fork 315
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
Automated test: XML file include #100
Comments
Hi, Although your feature is very reasonable, I'm now buried with another tasks and, as you perhaps have noticed, don't even have time to do bug fixing in nRF Connect :( PS. Any other feedback regarding automated tests? Still setting up the GATT server is unimplemented. |
Hi, I don't know how the test runner in nRF connect works. Maybe it would be a solution to specify two files: The actual test file as it is today plus a seconds one containing common data. The test runner could try to find elements in the common data which are not found in the test file. This would kind of emulate a include with the limitation that exactly one file could be included ... hmm. Would be good enough for me but also some effort and limitations in the result. I guess we will implement a small build step before uploading our test file to nrf and do code replacement on the fly before uploading the file to the phone. But thank you for your answer. Regards |
You may already specify extras in the command (in batch we use -E for that, afair, but you can check for the extra is passed to the service. Not ideal, but at least not in the xml. |
I am writing automated tests with nRF connect. When running a test I need to specify the tests inside an XML file.
When writing multiple tests in multiple files I found no way to include fragments, for example expected service or advertisment data. Thus, I need to copy & paste it in each XML file.
It would be great if the tests would support XML includes. I tried to use XML standard:
and then inside the file:
&chap1;
This does not seem to work. Implementing this or another way for imports would be great.
The text was updated successfully, but these errors were encountered: