1. What is an OMA SpecWorks TestFest?
OMA TestFests are designed to achieve a number of goals, including:
- Ensuring the quality of OMA specifications
- Enabling vendors to verify and test the interoperability of their product implementations in a multi-vendor environment
- Provide a peer-to-peer networking environment for participants
TestFests are held in a confidential and secure testing environment where companies can bring their Client or Server implementation(s) based on an OMA Enabler to test in multiple multi-vendor combinations. These events are open to both OMA member and non-member companies.
2. When is the next TestFest?
There are 1 to 2 TestFest events held per year. These events are hosted in a variety of locations and venues throughout North America, Europe, and Asia. Registration fees are per implementation (engineers are free to attend) and vary based on the expenses estimated to cover the event. If you are interested in hosting a TestFest at your company’s facility, please contact our staff.
3. Prerequisites for a TestFest
TestFests are open to the public, as long as you fulfill the following criteria for entry to the event:
- You have a unique implementation of an OMA Enabler, developed by the company or in direct association with a third party
- You have implemented all mandatory features of the Enabler to be tested
- You have passed any entry conformance or other preparatory tests defined for the event, listed in the appendix section of the Enabler Test Specifications: “Entry Criteria for a TestFest”
- You have signed a Non-Disclosure Agreement (NDA), provided by OMA, prior to attending the TestFest
4. Registering for a TestFest
The registration link for each event will be included with the TestEvent date and location on the TestFest homepage. During registration, you will be asked to select which OMA SpecWorks Enabler you will be testing and if you are a Client or Server. The specified fee for that event will be due upon registering and the event information will inform you what the fee covers / includes for the event.
Once registration closes, OMA SpecWorks staff will create a formal testing agenda that will be distributed to participants on-site. More detailed travel and event information, including recommendations on where to stay, a general overview of the schedule, arriving at the TestFest, and what to expect on-site, will be distributed via email to all participants as registration is in progress and once registration closes.
Participating teams may download the test material to be used during the event under each Enabler.
5. Reporting Test Session Results
When on-site, the Client teams will be required to complete a Test Session Report for each test session, verified by the Server team. These reports record the results that apply to all of the test cases that are part of the Enabler Test Specification defined by the members. Each report is confidential to the companies participating in that session.
At the end of the TestFest, OMA SpecWorks publicly posts the results of the event on the LwM2M for Developers Wiki page via GitHub. In the right hand column, you will see the name of each TestFest event listed. When you click on an event, a summary of the results are available for download (PDF). This report is an indication to the OMA SpecWorks Technical Plenary of both the completeness of the Specification as well as the quality of the implementations that are being tested.
Lastly, OMA SpecWorks hosts a Product Listings page on GitHub as well. Participating companies have the opportunity to market your product which features the OMA Enabler tested.
6. Reporting Issues with the Specification
One of the important aspects of any interoperability testing session is to record and process the problems found in the implementations being tested. In order for the relevant working groups to determine how a problem should be resolved, TestFest participants may have the opportunity to raise their queries directly with the corresponding Technical Working Group.
For LWM2M Test events, participants are asked to submit any issues they encounter with the specification on the OMA GitHub Issue Reporting Tool, which is monitored by the Device Management Working Group.