nickvachara / BusinessPlan

0 stars 0 forks source link

temp #1

Open nickvachara opened 4 years ago

nickvachara commented 4 years ago

: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, and NativeApi.

: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

: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.

nickvachara commented 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:

:point_down: Triage (bb62b6ad:maincv_4.0.0.8297ccc)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

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

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:pointdown: Triage (971f0109:maincv efce3dc)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

QA Summary

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:

:point_down: Triage (e5728ab8:maincv_efce3dc)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors
:+1: Generation
:phone: ReLocalization
:pager: Neither

:ledger: Notes

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

name: Quality Assurance Report about: A check list for basic quality assurance of the YOUAR Cloud SDK title: '' labels: enhancement assignees: gblikas


:point_down: Triage YOUAR Cloud SDK v6.1.1

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

Seems fine. But here are things I've noticed

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:point_down: Triage lockar-sdkv6.2.2_maincv_efce3dc.apk

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

Seems fine. But here are things I've noticed

original offset for anchor L Screenshot_20200814-170743_ARCloud

after shaking the phone and lost tracking Screenshot_20200814-170306_ARCloud

_tracked back but anchor L is now in the wrong offset Screenshot_20200814-170312_ARCloud Screenshot_20200814-170300_ARCloud

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:point_down: Triage (40ef2b2:maincv_efce3dc)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

The plugin used in this branch is not up-to-date with stagging. Using plugin from commit [728645d]

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:point_down: Triage (Short-Commit-HashGoesHere:maincv_Short-Commit-HashOfPluginGoesHere)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:point_down: Triage (9b7f37f:maincv_017c4a8)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:point_down: Triage (lockar-sdkv6.3.5_maincv_017c4a8.apk)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

No additional notes were given.

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

:point_down: Triage (40d7b99:maincv_690ec52)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:ledger: Notes

No additional notes were given.

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

QA Summary

:point_down: Triage (f3ddb40b:690ec52)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation
:phone: ReLocalization
:pager: Neither

:ledger: Notes

:chart_with_downwards_trend: Logs

here's a log i was able to grab after one of the crashes output.txt


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 4 years ago

QA Summary

:point_down: Triage (fd72b5a7:690ec52)

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:

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Behaviors

:+1: Generation
:phone: ReLocalization
:pager: Neither

:ledger: Notes

:chart_with_downwards_trend: Logs

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


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 3 years ago

name: Quality Assurance Report about: A check list for basic quality assurance of the OMEP AR Viewer title: '' labels: enhancement assignees: gblikas; Lukehartwig; json-x-ly

:point_down: Triage (Short-Commit-HashGoesHere)

: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.

QA Summary

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:

Authentication and Credentials

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:

UI

The following diagram(s) show what the UI Screen should look like (including error handling iconograpy and variations)

// img goes here

UX

:ledger: Notes

Did not test for anything else beyond logging in and verify the errors pertaining to this issue is fixed

:chart_with_downwards_trend: Logs

No (crash) logs were given.

:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.

nickvachara commented 1 year ago

:point_down: Triage (a81bf3b1:maincv_9a94380)

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.

: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, and NativeApi.

:anchor: Lockar

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.

:two_hearts: SDK Integrations

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.

:smile: Visualization

:smile: Behaviors

:+1: Generation

:phone: ReLocalization

:pager: Neither

:dog: Functions

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.

Raycast

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.

Generation

These checks are assumed to be in the same runtime.

:ledger: Notes

  1. While creating the anchor. Raycasted to create on object. Upon reacquiring the object was off by approximately 0.1-0.2 meters. Tried to recreate what I saw resulting in the images below. Though the following 2nd and 3rd time didn't seem to be off by much (negatable?)
Create Localize
  1. 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

  2. Tracked to 1st and 2nd anchor. Created 3rd anchor. During reacquiring the graph. Noticed the object from 1st anchor had dramatically drifted

General

:chart_with_downwards_trend: Logs

No (crash) logs were given.


:books: Final Summary

If any of the previous check boxes have not been checked, this build fails.