Welcome to the OMA TestFest Overview pages. The following information should provide you with everything you need to know about applying to attend and participating in an OMA TestFest and designed to help you understand what TestFests are about, what they are for and what will happen during the event.

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.

Links Overview
Next TestFest Details

Date: 08 Oct – 12 Oct 2018
Location:USA – Austin (Texas)
Registration will open 10 Aug 2018

What is a 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
Prerequisites for the 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

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 the OMA staff

Register for a Testfest

During registration, you will be asked to select which OMA 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 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

Product Listing for LightweightM2M

Latest Testfests

  • LwM2M TestFest Event in Seoul - July 2018
  • LwM2M TestFest Event in Warsaw - Nov 2017
  • LwM2M TestFest Event in Pitsburgh - May 2017
  • LwM2M TestFest Event in Singapore - October 2016
  • LwM2M TestFest Event in San Diego, CA, USA - January 2016

Problem Reporting

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.


Links Overview
User Agent Profiles
  • This link provides an open-source library developed at HP Labs that allows Java servlets to resolve HTTP requests containing CC/PP or UAProf information and query the resolved profile.

UAProf Validator
  • Different web-enabled devices have different input, output, hardware, software, network and browser capabilities. In order for a web server or web-based application to provide optimized content to different clients it requires a description of the capabilities of the client known as the delivery context. Recently two new compatible standards have been created for describing delivery context: Composite Capabilities / Preferences Profile (CC/PP) created by the W3C and User Agent Profile (UAProf) created by the WAP Forum.

eMO Editor
  • This tool contains a Management Object Editor, eMO, together with the relevant functionality to import, export, view and create new Management Objects (MOs). Tool Guideline

eLWM2M Editor
  • The LightweighM2M tool contains an editor eLwM2M and the relevant functionality to import, export, view and create new Objects and Resources. Tool Guideline

LwM2M Registry - API Service
  • This service provides all the necessary information to interact with the OMA LwM2M Registry, also called OMNA (OMA Naming Authority)