Open nickvachara opened 4 years ago
Candidate for the YOUAR Cloud SDK v4.0.1 using maincv_4.0.0.8297ccc, as reported by the internal plugin. Below is the QA list for this PR:
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
When neither relocalize or generating; Move More
coach isn't activated.
Makes sense that it doesn't. Perhaps it shouldn't be in the check list
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
Unload Anchor
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Testing the internal pipeline with <!--- FULL NameSpaces, e.g. Uber, Lockar, and Uber.Statistics --->, we have the following QA checklist completion. The following list of devices was used to compile this QA report:
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
Trackable
belonging to a different Anchor
. aAnchor
we're trackaing too in the UI
08-03 15:35:16.782 18452 18478 E Unity :
08-03 15:35:16.782 18452 18478 E Unity : (Filename: <30f53270fb70478f837412aa9447ce3c> Line: 0)
08-03 15:35:16.782 18452 18478 E Unity :
08-03 15:35:16.812 18452 18478 W Unity : Node for this graph 8900677d-2a44-4a3c-8bc0-49e012f39252 not in Anchor: 3018e43e-828e-4822-9ac8-47e22fcae9fd
08-03 15:35:16.812 18452 18478 W Unity :
08-03 15:35:16.812 18452 18478 W Unity : (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)
08-03 15:35:16.812 18452 18478 W Unity :
08-03 15:35:16.812 18452 18478 W Unity : NODE_GRAPH ADD ERROR: NodeGraph not found in runtime cant add trackable 3018e43e-828e-4822-9ac8-47e22fcae9fd as node
08-03 15:35:16.812 18452 18478 W Unity :
08-03 15:35:16.812 18452 18478 W Unity : (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)
08-03 15:35:16.812 18452 18478 W Unity :
08-03 15:35:16.814 18452 18478 W Unity : Node for this graph 8900677d-2a44-4a3c-8bc0-49e012f39252 not in Anchor: 3018e43e-828e-4822-9ac8-47e22fcae9fd
08-03 15:35:16.814 18452 18478 W Unity :
08-03 15:35:16.814 18452 18478 W Unity : (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)
08-03 15:35:16.814 18452 18478 W Unity :
08-03 15:35:16.818 18452 18478 E Unity : NullReferenceException: Object reference not set to an instance of an object
08-03 15:35:16.818 18452 18478 E Unity : at LockarAlertManager.OnNodeAdded (Lockar.Node obj) [0x00000] in <30f53270fb70478f837412aa9447ce3c>:0
08-03 15:35:16.818 18452 18478 E Unity : at (wrapper delegate-invoke) System.Action`1[Lockar.Node].invoke_void_T(Lockar.Node)
08-03 15:35:16.818 18452 18478 E Unity : at Lockar.NodeGraphDriver.OnMultimapEventComplete (Uber.Trackable trackable) [0x00156] in <3003879bcc1f4471a8e19ee8c570ba3e>:0
08-03 15:35:16.818 18452 18478 E Unity : at (wrapper delegate-invoke) <Module>.invoke_void_Trackable(Uber.Trackable)
08-03 15:35:16.818 18452 18478 E Unity : at Uber.Api.TrackableApi.Update (UnityEngine.Matrix4x4 matrix, System.Int32 indexOfTrackable) [0x000d9] in <84fb7926ad414eac834f97374322d5e8>:0
08-03 15:35:16.818 18452 18478 E Unity : at Uber.FrameInterface.Update () [0x000bb] in <84fb7926ad414eac834f97374322d5e8>:0
Anchor
or Trackable
updatesNiether
, the coach Move More
doesn't show up; perhaps? we could create a coach to let user
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
name: Quality Assurance Report about: A check list for basic quality assurance of the YOUAR Cloud SDK title: '' labels: enhancement assignees: gblikas
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
Seems fine. But here are things I've noticed
Reorient Device
coach which means it's tracking better, which is good? Or there just might be better lighting in my room today,Move Smoothly
coach seems not to be easily triggered by wide horizontal back and forth swing anymore. Just something I'd noticedUnload Anchor
even though i'm scanning and successfully saving the same area in 4 separate scans. 3 of which was consolidated into the same graph, but still couldn't trigger this coachNo (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
Seems fine. But here are things I've noticed
Move Smoothly
coach seems not to be easily triggered by wide horizontal back and forth swing.Unload Anchor
.Move More
coach isn't triggered under neither (not generating, not relocalizing)ARCore
during the test but couldn't recreate. Happen while shaking the phone to trigger Move Smoothly
coach and Reorient Device
coach showed up then lost tracking to ARCore
. Don't have a log for this incident.original offset for anchor L
after shaking the phone and lost tracking
_tracked back but anchor L
is now in the wrong offset
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
The plugin used in this branch is not up-to-date with stagging. Using plugin from commit [728645d]
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
true
when we start the app regardless of previous settingNo (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
No additional notes were given.
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
No additional notes were given.
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
here's a log i was able to grab after one of the crashes output.txt
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following list of devices was used to compile this QA report:
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
here are outputs from my crashes output.txt output(2).txt output(3).txt
ps. the full *.zip of the data folders are too large to post here
If any of the previous check boxes have not been checked, this build fails.
:exclamation: Failure to fill out all fields can result in immediate cause for rejection.
Did the commit check all of the following boxes for basic application functionality? The quality assurance report is meant to buffer any preliminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
You have the option of submitting an incomplete or paired-down QA report. However, the failure of the feature set is your entire responsbility, and you might be asked to work extra to resolve any issue incurred by NOT DOING THE FULL QA CHECKLIST.
The following list of devices was used to compile this QA report:
Here is a quick summary of the QA checklist(s) for omeparviewer:
This section is about loging in to and using credentials for the omeparveiwer. If you are loggin in with more than one account, please make sure you run all tests under each seprate user; if there is an issue with QA and you've used more than one account and didn't check, the responsibility falls on your sholders.
The following user-names and passwords were used with the given permissions:
The following diagram(s) show what the UI Screen should look like (including error handling iconograpy and variations)
// img goes here
Did not test for anything else beyond logging in and verify the errors pertaining to this issue is fixed
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any pre-liminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
Checks for the internal Trackable creation pipeline. This takes into account the TrackableApi
, PointCloudApi
, and NativeApi
.
Checks for the internal relative positioning engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functinality represents the more primary integrations with our SDK, typically managed by other team memebers outside of the core team.
This section covers other integrations that happen at the functional level inside the SDK. These are usually button presses or custom build settings from the SDK.
This section of checks covers RayCastApi and how it behaves in responsiveness, load, and functionally when practically integrated. All checks need to make sure that the number of calls is recorded, as it is a good indicator for performance and backwards compatibility.
These checks are assumed to be in the same runtime.
Create | Localize |
While already tracked to 1st anchor, I'd turn the phone to the left of my room and created a 2nd anchor. During that creation, all raycast to spawn objects was spawning the objects off-centered
Tracked to 1st and 2nd anchor. Created 3rd anchor. During reacquiring the graph. Noticed the object from 1st anchor had dramatically drifted
General
No (crash) logs were given.
If any of the previous check boxes have not been checked, this build fails.
:point_down: Triage (350e9647:maincv_7ea35c5)
Did the commit check all of the following boxes for basic plugin functionality? The quality assurance report is meant to buffer any preliminary functionality that might be broken before a major merge into master is done. In the future, this will be required before all merges into staging as well.
:dragon: Core SDK
The following check list tests the core functionality inside of the YOUAR Cloud SDK, irrespective of any higher-level functionality like Coaching, or Examples. Note: Examples can fail, while this list passes, or visa versa.
:bird: Uber
Checks for the internal Trackable creation pipeline. This takes into account the
TrackableApi
,PointCloudApi
, andNativeApi
.:anchor: Lockar
Checks for the internal relative position engine, otherwise known as Lockar. This primarily deals with the NodeGraphDriver, and its objects. This covers relative positioning checks for the 4 tiers of relative positioning that we currently have.
:two_hearts: SDK Integrations
A quality assurance report for functionality above the YOUAR Cloud SDK core functionality, but below examples. This functionality represents the more primary integrations with our SDK, typically managed by other team members outside of the core team.
:smile: Behaviors
:+1: Generation
:phone: ReLocalization
:pager: Neither
:ledger: Notes
LockAR
Unload Anchor
even though 3 of the scans were generally the same area started scanning from the same pointUnload Failure
when trying toDownload Graphs
Move Smoothly
(movement speed) did NOT have priority overNormalize Feature
andNormalize Light
during the [Neither] test caseMove Smoothly
to activate when moving device over 1.5 feet (approximately); in which if Generating or Relocalizing tracking would be lost andReorient Device
coach would get activated instead.reorient device
would NOT disengage if tracked to a different anchor while it was activated.reorient device
was activated, it's corrected state would not get called.:chart_with_downwards_trend: Crash Log
No crash logs were given.
:books: Final Summary
If any of the previous check boxes have not been checked, this build fails.