Skip to main content

Browse the archive

Revision 2877f572684541d6cd2f301d72f4114dd35ce885 authored by Robert Ma on 24 July 2018, 22:40:00 UTC, committed by Philip Jägenstedt on 25 July 2018, 09:01:10 UTC 
Fix resources/test suite
 
The suite was broken by PR #11976 where the config class was changed.
The suite uses a hack to get the default config of wptserve. This commit
fixes the hack, but unfortunately does not find a less hacky way to get
the default config.
1 parent 0589266
Raw File
nfc_recordType_empty-manual.https.html 
<!DOCTYPE html>
<meta charset=utf-8>
<title>Web NFC Test: push and watch empty records</title>
<link rel="author" title="Intel" href="http://www.intel.com"/>
<link rel="help" href="https://w3c.github.io/web-nfc/"/>
<meta name="timeout" content="long">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="resources/nfc_help.js"></script>
<meta name="flags" content="interact">

<p>Tap an NFC tag to the test device with NFC support.</p>

<p>Note: All the actions need to be done in 60 seconds, otherwise it will get TIMEOUT.</p>

<div id="log"></div>

<script>

"use strict";

setup({ explicit_timeout: true });

let desc = "Test that nfc.push and nfc.watch succeed when recordType is set to 'empty'.";
let watchOptions = {
  recordType: "empty",
  mediaType: "",
  url: ""
}
let message = createMessage([createRecord('empty', '')]);

testNFCMessage(message, watchOptions, desc);

</script>
back to top