-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Heartbeat Study survey #182
Conversation
@@ -0,0 +1,9 @@ | |||
package edu.stanford.bdh.heartbeat.app.fake | |||
|
|||
object FakeConfigs { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pauljohanneskraft you can simulate a fake flow via this object. If enabled it runs a survey from data of a json file that contains at least one question of the field types that we should implement
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## task/heartbeat-app #182 +/- ##
========================================================
- Coverage 33.15% 33.10% -0.04%
Complexity 771 771
========================================================
Files 277 278 +1
Lines 11338 11355 +17
Branches 1817 1818 +1
========================================================
Hits 3758 3758
- Misses 7337 7354 +17
Partials 243 243
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
Amazing for all the work here @eldcn! 🚀 |
add missing required fields send question metada info - retry count, render time and think time in millis render optional title 2 addapt fake data json improve logging
Heartbeat study survey
♻️ Current situation & Problem
⚙️ Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.
Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
📚 Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
✅ Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.
This section describes important information about the tests and why some elements might not be testable.
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: