QA/MozVR: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 17: Line 17:
To be filled; Test plan for https://github.com/aframevr/aframe : A-Frame is a framework for creating virtual reality web experiences.
To be filled; Test plan for https://github.com/aframevr/aframe : A-Frame is a framework for creating virtual reality web experiences.


== Is the browser webVR ready? ==
== Website tests ==
https://iswebvrready.org/faq
=== MozVR ===
* test plan TBD
** check links on mozvr.com
=== aframe.io ===
* test plan TBD
** check links on aframe.io
=== Is the browser webVR ready? ===
* test plan for https://iswebvrready.org/faq tbd.
** need to add samples.


= FAQ =
= FAQ =

Revision as of 04:33, 26 April 2016

Introduction

This webpage is a comprehensive webpage on all the things that QA will be looking at in order to get VR into the web, including and not limited to : WebVR API in desktop, mobile, WebVR-polyfill, and Aframe. The webvr concept is explained here.

WebVR API

The scope of the testing will be covered in the WebVR Test plan for the webVR API This covers setup and scope of testing for the desktop browser and oculus rift.

WebVR Polyfill

To be filled; Test plan to provide webvr support for Cardboard devices : https://github.com/borismus/webvr-polyfill

WebVR BoilerPlate

To be filled; Test plan for https://github.com/borismus/webvr-boilerplate ; A THREE.js-based starting point for VR experiences that work well in both Google Cardboard and other VR headsets. Also provides a fallback for experiencing the same content without requiring a VR device

Aframe

To be filled; Test plan for https://github.com/aframevr/aframe : A-Frame is a framework for creating virtual reality web experiences.

Website tests

MozVR

  • test plan TBD
    • check links on mozvr.com

aframe.io

  • test plan TBD
    • check links on aframe.io

Is the browser webVR ready?

FAQ

  • meeting:
  • contacts:
  • how to contribute to testing


Misc stuff to be evaluated