crosswalk-project/crosswalk-test-suite

crosswalk-test-suite's Issues

[webapi][wrt][cordova] Move 'testkit/web' to 'webrunner'

Hi @jennycao, @cicili and @ibelem,

Because webrunner has been released as a separate project (https://github.com/testkit/webrunner) rather than a sub-directory of the testkit-lite project, I think we'd better move the files in 'testkit/web' to 'webrunner' in each test suite. What's your opinion?

I just tried 2dtransforms test suite, only configure.ac, Makefile.am, pack.sh in the root of the test suite and webrunner\Makefile.am are modified.

I suggest @haoyunfei take this issue and make a pull request for all test suites. When this is done, @haoyunfei can apply the same improvement to TCT 2.3 test suites.

Thanks,
@zqzhang

[webapi][runtime] Multiple features in spec_url

In https://github.com/crosswalk-project/crosswalk-test-suite/blob/master/webapi/webapi-runtime-xwalk-tests/runtime/spec.json#L3, the spec_url is assigned to be https://crosswalk-project.org/jira/browse/XWALK-516,XWALK-596,XWALK-597 which shall be 3 JIRA features.

Question: shall spec_url support multiple URLs?

If no, my suggestion is to put one main feature link here and to link all the features in JIRA system using More -> Link.

[wrt][webapi] Need tests for <tizen:setting screen-orientation> can be changed by the W3C Screen Orientation API

When I reviewed #226, I realized that besides W3C Screen Orientation API Tizen Web Runtime core spec also have a screen-orientation configuration extension:

• screen-orientation (optional, available values: portrait (default), landscape, auto-rotation)
o   portrait: Web Application view-port orientation MUST be locked to portrait by default.
o   landscape: Web Application view-port orientation MUST be locked to landscape by default. 
Since: 2.0
o   auto-rotation: If the system's auto-rotation setting is on, the Web Application view-port orientation MUST be changed according to the device orientation by default.
Since: 2.2
Note: In any configuration, the screen orientation can be changed by the W3C Screen Orientation API.

So, from WRT part, we need 4 tests at least to check (1) the three values of the screen-orientation and (2) screen orientation can be changed by the W3C Screen Orientation API.

From WebAPI part, we need comprehensively check that the lockOrientation and unlockOrientation APIs are able to change the screen orientation set by screen-orientation extension.

Any feedback is welcome.

Update documentation

Background

In this repository, we have various documents, README.md, README file in each test suite, developer/user guides and packaging guide in docs/.

For one thing, these documents have gotten out of date with the code which has lots of changes since documents revised; for another, the PDF version documents in docs\ are difficult to maintain.

Goal

• To bring the docs up to date.
• To remove low-value documentation and make it easier to find the relevant documentation when working with tests.
• To make future maintenance of the documentation easier.

Proposal

• Update README.md in this structure:
  • Getting Started
  • Writing Tests
  • Running Tests
  • Submitting Tests
  • Reviewing Tests
  • Reporting Bugs
• Rewrite the PDF version developer/user guides in Markdown
  • Behavior_Test_Tool_Developer_Guide.md
  • Behavior_Test_Tool_User_Guide.md
  • Coding_Style_Guide_CheatSheet.md
  • Cordova_Test_Suite_User_Guide.md
  • WebAPI_Test_Suite_User_Guide.md
  • Web_BAT_Test_Suite_User_Guide.md
  • Web_Runtime_Test_Suite_User_Guide.md
  • Web_Test_Suite_Developer_Guide.md
  • Web_Test_Suite_Packaging_Guide.md
• Revise README in each test suite in Markdown
• Create developer guides for new test suites (optional)
  • Cordova
  • Embedding API
  • SIMD
  • WRT, including Pairwise based WRT tests

[webapi] Change test priority from P0 to P1

As doc/Web_Test_Suite_Developer_Guide_v1.0.pdf specified, P0 is used for use-case tests only now. However, there are some P0 tests under webapi\; please @haoxli and @Honry take care of this, thanks.

crosswalk-test-suite/webapi$ grep 'priority="P0"' -l */*.xml
tct-calendar-tizen-tests/tests.full.xml
tct-contact-tizen-tests/tests.full.xml
tct-deviceorientation-w3c-tests/tests.full.xml
tct-filesystem-tizen-tests/tests.full.xml
tct-namespace-tizen-tests/tests.full.xml
tct-sse-w3c-tests/tests.full.xml
tct-testconfig/tests.full.xml
tct-time-tizen-tests/tests.full.xml
tct-xmlhttprequest-w3c-tests/tests.full.xml
webapi-ambientlight-w3c-tests/tests.full.xml
webapi-deviceadaptation-css3-tests/tests.full.xml
webapi-imports-w3c-tests/tests.full.xml
webapi-messaging-sysapps-tests/tests.full.xml
webapi-promises-nonw3c-tests/tests.full.xml
webapi-runtime-xwalk-tests/tests.full.xml
webapi-taskscheduler-sysapps-tests/tests.full.xml
webapi-webrtc-w3c-tests/tests.full.xml

Combine `slider.tooltip.js` files into `js/thirdparty/`

At #863, I find WRT people is trying to add slider.tooltip.js file to use-case test.

At current being, the crosswalk-test-suite contains several copies of slider.tooltip.js file, but they are not the same. Why not combine them together? For example, put it into <test-suite>/js/thirdparty/.

• behavior/tests/2D3DAnimation/js/slider.tooltip.js
• behavior/tests/CSSStyle/js/jquery/slider.tooltip.js
• behavior/tests/MediaPlayback/js/jquery/slider.tooltip.js
• behavior/tests/Vibration/js/jquery/slider.tooltip.js
• usecase/webapi-usecase-tests/tests/AudioPlay/js/jquery/slider.tooltip.js
• usecase/webapi-usecase-tests/tests/CSSStyle/js/jquery/slider.tooltip.js
• usecase/webapi-usecase-tests/tests/Vibration/js/jquery/slider.tooltip.js
• usecase/webapi-usecase-tests/tests/VideoPlayAndroid/js/jquery/slider.tooltip.js
• usecase/webapi-usecase-tests/tests/VideoPlayTizen/js/jquery/slider.tooltip.js
• usecase/webapi-usecase-tests/tests/WebGL/js/slider.tooltip.js

XWALK-2229 Add test case for white flash between application transitions

When launching an app from the homescreen or returning to the homescreen, there is a white layer overlay that appears between the animations.
For more details, please check https://crosswalk-project.org/jira/browse/XWALK-2229

Figure out WebAPI specifications difference between Chromium implementation and Crosswalk test suites

Background

1. In each milestone, Crosswalk rebases to latest Chromium Beta. For example, at XWALK-2431, Crosswalk 9 rebases to Chromium 38. Therefore, Crosswalk shall enable the Chromium Web Platform Features which are enabled by default on Chromium Beta.
2. Crosswalk-test-suite once leverage many test suites from TCT 2.2.1, webapi/tct-*-tests. These test suites were created based on Tizen 2.2.1 Web API References, which may have different specification version from Chromium Web Platform Features. For example, Tizen 2.2.1 supports http://www.w3.org/TR/2012/WD-screen-orientation-20120522, while Chromium 38 supports the latest Screen Orientation API at https://w3c.github.io/screen-orientation/ ; and that's why we update test cases at https://crosswalk-project.org/jira/browse/XWALK-2372
3. Crosswalk-test-suite also create some test suites, webapi/webapi-*-tests, for Crosswalk Features, which may also have different specification version from Chromium Web Platform Features.

Action

1. Figure out WebAPI specifications difference between Chromium implementation (http://www.chromestatus.com/features) and Crosswalk test suites.
2. Update Crosswalk test suites accordingly to reflect Chromium implementation, with one task report per spec. Please refer to https://crosswalk-project.org/jira/browse/XWALK-2372

Redesign behavior/usecase test suites UI

Background

At current being in this repository, all behavior-like test suites (behavior, usecase and misc/xwalk-system-tests) contain 3 resource files:

• css/main.css: style sheet for img and h1 of page/content/listview based on jquerymobile, and for overlay, button hidden and shown, and fontSizen.
• js/main.js:
• js/tests.js:

The css/main.css file is referenced by index.html and all test case files; js/main.js is referenced by index.html and some test case files; js/tests.js is referenced by all test case files. This is not good.

Redesign

• Separate css/main.css into css/style.css and css/uicust.css with targets that (1) the former is used only for the root index.html, and (2) the latter for individual test case layout based on jquerymobile with reference to Bootstrap Grid System.
• Combine and separate js/main.js and js/tests.js into js/main.js and js/uicust.js with targets that (1) the former is used only for the root index.html, and (2) the latter for individual test case user interaction based on jquerymobile.

Therefore, the test suites will have 4 resource files:

• css/style.css and js/main.js for the test suite root index.html layout and user interaction;
• css/uicust.css and js/uicust.js for individual test case index.html layout and user interaction; where uicust means UI Customization.

XWALK-2216 Add test case for Modello app's icon source check after app has been installed

All the Modello installed using xwalkctl -i xxxx.wgt do not have their app icons installed properly and populated, and calling tizen.application.getAppsInfo().iconPath will not return the correct app icon specified in the manifest.
After installation, you can see that every app's icons installed to /usr/share/icons/default/small/ uses the same icon image, and not the icon from the wgt.
For more details, please check https://crosswalk-project.org/jira/browse/XWALK-2216

[tools] Need a script to stats test case number

More often we are asked to provide data like test case number in total and various of types. I think we'd better create a script to do this, e.g. stats.py, then we can easily generate such kind of statistics from the root by python tools\coverage\stats.py.

At current being, each test suite has a tests.full.xml that has 2 elements <suite> and <testcase> being able to generate data like:

Summary

Category	Total	Auto	Manual	Approved	Designed	P0	P1	P2	P3
behavior
cordova
embeddingapi
misc
webapi
webdriver
wrt

... and details if there are 2+ test suites in each category (1st level sub-directory in this repo)

WebAPI

Test Suite	Total	Auto	Manual	Approved	Designed	P0	P1	P2	P3
tct-2dtransforms-css3-tests
webapi-ambientlight-w3c-tests
...

The output data can be either an .html or .xml file.

Besides running across the whole repo, the script shall be able to iterate a sub-directory, e.g. webapi/, and to scan a specific test suite, e.g. webapi/tct-2dtransforms-css3-tests/tests.full.xml

XWALK-2231 Add test case for media source API test pause

media source API test pause in the 4th chunk sometimes.
For more details, please check https://crosswalk-project.org/jira/browse/XWALK-2231

Make github pages

Background

Crosswalk test suite has many test cases that are able to be running in web testing service mode. However, there is not a public instance of server due to various of reasons. Therefore people has to use an internal instance for bug reporting and reproducing.

Yeah it is able to leverage the GitHub Pages that are served over HTTP for public webpages freely hosted and easily published through github.io

Creating Pages

It is very easy to create github pages for an existing github project. @zqzhang has just created one for this repository via

$ git clone [email protected]:crosswalk-project/crosswalk-test-suite.git
$ git checkout -b gh-pages
$ git push origin gh-pages

See https://github.com/crosswalk-project/crosswalk-test-suite/tree/gh-pages

Using the Pages

There are several usages of these pages:

• Report bugs with test code online, e.g. http://crosswalk-project.github.io/crosswalk-test-suite/webapi/tct-2dtransforms-css3-tests/2dtransforms/csswg/2d-transforms.html
• Reproduce bugs via a .wgt or .apk with Crosswalk embedded to access the test code online
• Run the test code online with Chrome/Chromium/Firefox for comparison

Maintaining the Pages

At current being, resource files have been centralized into tools/resources/; we have to restore them for the Pages via python tools/build/copy.py. See f0c6696

Therefore, after each sync with the master branch (using git reset --hard HEAD^, git rebase master and git push origin gh-pages), the maintainer must restore the resource files.

To Do

To easy test case running and bug reporting/reproducing, an index.html like https://github.com/crosswalk-project/web-testing-service/blob/master/wts/runner/index.html shall be provided, and a .wgt or .apk with Crosswalk embedded packaging scripts to access the test code online is needed too.

Known Issue

• Visit http://crosswalk-project.github.io/crosswalk-test-suite/behavior/index.html getting error message "Failed to load resource: the server responded with a status of 404 (Not Found)" for the http://crosswalk-project.github.io/crosswalk-test-suite/behavior/js/thirdparty/jquery.js; because "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/."

XWALK-2199 Add hide() check for hide/recover several times

XWALK-2199 tizen.application.getCurrentApplication().hide() works once

[Belem] There are test cases about hide() in tct-application-tizen-tests/application, bu do we have this scenario?
[Cao, Jenny Q] same issue with Xwalk-2168, the root cause is that wyland issue on windows.minimize(): bug intel/ozone-wayland#258
[Cao, Jenny Q] To Test suite, we could Add hide() check in the usecase, hide/recover several times.

XWALK-2191 Add a TC for ART mode in misc/system

XWALK-2191 SEGV_MAPERR error appears in Android 4.4.4 devices
[Belem] Both Chrome and Crosswalk get crash when running in ART mode. We need test cases for ART mode besides dalvik mode by default on Android. (Android 4.4 or higher, not for ZTE Geek which is 4.2.2)
[Cici] Add a TC for ART mode in misc/system

[tools] Check tools/build/pack.py with pylint

@yugang just check tools/build/pack.py with pylint on Ubuntu 12.04, and get error message as below. Seems we need to create a configure file for the Python code static checker as we will update all the packaging and installing/uninstalling scripts using Python.

No config file found, using default configuration
************* Module pack
C:  5,0: Line too long (82/80)
C:  8,0: Line too long (81/80)
C:325,0: Line too long (83/80)
C:384,0: Line too long (93/80)
C:396,0: Line too long (99/80)
C:419,0: Line too long (119/80)
C:422,0: Line too long (98/80)
C:433,0: Line too long (119/80)
C:469,0: Line too long (114/80)
C:470,0: Line too long (84/80)
C:476,0: Line too long (98/80)
C:477,0: Line too long (94/80)
C:479,0: Line too long (156/80)
C:480,0: Line too long (103/80)
C:506,0: Line too long (89/80)
C:511,0: Line too long (99/80)
C:526,0: Line too long (105/80)
C:544,0: Line too long (144/80)
C:551,0: Line too long (82/80)
C:566,0: Line too long (92/80)
C:592,0: Line too long (135/80)
C:602,0: Line too long (87/80)
C:610,0: Line too long (103/80)
C:614,0: Line too long (121/80)
C:618,0: Line too long (117/80)
C:622,0: Line too long (119/80)
C:631,0: Line too long (121/80)
C:673,0: Line too long (124/80)
C:675,0: Line too long (107/80)
C:676,0: Line too long (112/80)
C:708,0: Line too long (104/80)
C:727,0: Line too long (124/80)
C:737,0: Line too long (91/80)
C:749,0: Line too long (104/80)
C:752,0: Line too long (81/80)
C:767,0: Line too long (96/80)
C:791,0: Line too long (86/80)
C:793,0: Line too long (96/80)
C:795,0: Line too long (95/80)
C:797,0: Line too long (87/80)
C:799,0: Line too long (102/80)
C:801,0: Line too long (94/80)
C:803,0: Line too long (91/80)
C:805,0: Line too long (119/80)
C:807,0: Line too long (101/80)
C:825,0: Line too long (91/80)
C:826,0: Line too long (89/80)
C:827,0: Line too long (87/80)
C:860,0: Line too long (82/80)
C:866,0: Line too long (88/80)
C:874,0: Line too long (88/80)
C:878,0: Line too long (88/80)
C:907,0: Line too long (82/80)
C:939,0: Line too long (115/80)
C:948,0: Line too long (87/80)
C:  1,0: Missing docstring
E: 45,0: Module 'sys' has no 'setdefaultencoding' member
C: 67,0:ColorFormatter: Missing docstring
C: 90,0:pidExists: Invalid name "pidExists" (should match [a-z_][a-z0-9_]{2,30}$)
C: 90,0:pidExists: Missing docstring
C: 95,22:pidExists: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W: 95,22:pidExists: Unused variable 'e'
C:101,0:IsWindows: Invalid name "IsWindows" (should match [a-z_][a-z0-9_]{2,30}$)
C:101,0:IsWindows: Missing docstring
C:105,0:KillProcesses: Invalid name "KillProcesses" (should match [a-z_][a-z0-9_]{2,30}$)
C:105,0:KillProcesses: Missing docstring
C:112,8:KillProcesses.GetChildPids: Invalid name "GetChildPids" (should match [a-z_][a-z0-9_]{2,30}$)
C:112,8:KillProcesses.GetChildPids: Missing docstring
W:133,20:KillProcesses: No exception type(s) specified
C:136,0:safelyGetValue: Invalid name "safelyGetValue" (should match [a-z_][a-z0-9_]{2,30}$)
C:136,0:safelyGetValue: Missing docstring
C:142,0:checkContains: Invalid name "checkContains" (should match [a-z_][a-z0-9_]{2,30}$)
C:142,0:checkContains: Missing docstring
C:148,0:getRandomStr: Invalid name "getRandomStr" (should match [a-z_][a-z0-9_]{2,30}$)
C:148,0:getRandomStr: Missing docstring
W:151,8:getRandomStr: Unused variable 'i'
W:169,16:zipDir: Redefining built-in 'file'
C:158,0:zipDir: Invalid name "zipDir" (should match [a-z_][a-z0-9_]{2,30}$)
C:158,0:zipDir: Missing docstring
W:174,11:zipDir: Catching too general exception Exception
C:174,22:zipDir: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:168,18:zipDir: Unused variable 'dirs'
C:181,0:overwriteCopy: Invalid name "overwriteCopy" (should match [a-z_][a-z0-9_]{2,30}$)
C:181,0:overwriteCopy: Missing docstring
W:200,19:overwriteCopy: Catching too general exception Exception
E:198,30:overwriteCopy: Undefined variable 'stat'
E:199,16:overwriteCopy: Module 'os' has no 'lchmod' member
C:200,30:overwriteCopy: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:200,30:overwriteCopy: Unused variable 'e'
C:208,0:doCopy: Invalid name "doCopy" (should match [a-z_][a-z0-9_]{2,30}$)
C:208,0:doCopy: Missing docstring
W:219,11:doCopy: Catching too general exception Exception
C:219,22:doCopy: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
C:226,0:doRemove: Invalid name "doRemove" (should match [a-z_][a-z0-9_]{2,30}$)
C:226,0:doRemove: Missing docstring
W:234,15:doRemove: Catching too general exception Exception
C:234,26:doRemove: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
C:240,0:updateCopylistPrefix: Invalid name "updateCopylistPrefix" (should match [a-z_][a-z0-9_]{2,30}$)
C:240,0:updateCopylistPrefix: Missing docstring
C:243,4:updateCopylistPrefix: Invalid name "PACK_TOOL_TAG" (should match [a-z_][a-z0-9_]{2,30}$)
C:258,0:buildSRC: Invalid name "buildSRC" (should match [a-z_][a-z0-9_]{2,30}$)
C:258,0:buildSRC: Missing docstring
C:284,0:exitHandler: Invalid name "exitHandler" (should match [a-z_][a-z0-9_]{2,30}$)
C:284,0:exitHandler: Missing docstring
C:299,0:prepareBuildRoot: Invalid name "prepareBuildRoot" (should match [a-z_][a-z0-9_]{2,30}$)
C:299,0:prepareBuildRoot: Missing docstring
W:301,4:prepareBuildRoot: Using the global statement
W:302,4:prepareBuildRoot: Using the global statement
W:303,4:prepareBuildRoot: Using the global statement
W:304,4:prepareBuildRoot: Using the global statement
W:305,4:prepareBuildRoot: Using the global statement
W:306,4:prepareBuildRoot: Using the global statement
W:307,4:prepareBuildRoot: Using the global statement
C:331,0:doCMD: Invalid name "doCMD" (should match [a-z_][a-z0-9_]{2,30}$)
C:331,0:doCMD: Missing docstring
C:352,0:doCMDWithOutput: Invalid name "doCMDWithOutput" (should match [a-z_][a-z0-9_]{2,30}$)
C:352,0:doCMDWithOutput: Missing docstring
C:381,0:packXPK: Invalid name "packXPK" (should match [a-z_][a-z0-9_]{2,30}$)
C:381,0:packXPK: Missing docstring
C:413,0:packWGT: Invalid name "packWGT" (should match [a-z_][a-z0-9_]{2,30}$)
C:413,0:packWGT: Missing docstring
C:429,0:packAPK: Invalid name "packAPK" (should match [a-z_][a-z0-9_]{2,30}$)
C:429,0:packAPK: Missing docstring
R:429,0:packAPK: Too many return statements (8/6)
R:429,0:packAPK: Too many branches (19/12)
C:502,0:packCordova: Invalid name "packCordova" (should match [a-z_][a-z0-9_]{2,30}$)
C:502,0:packCordova: Missing docstring
W:502,16:packCordova: Unused argument 'build_json'
R:502,0:packCordova: Too many return statements (9/6)
C:551,0:packEmbeddingAPI: Invalid name "packEmbeddingAPI" (should match [a-z_][a-z0-9_]{2,30}$)
C:551,0:packEmbeddingAPI: Missing docstring
R:551,0:packEmbeddingAPI: Too many local variables (16/15)
W:577,11:packEmbeddingAPI: Catching too general exception Exception
C:577,22:packEmbeddingAPI: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:604,11:packEmbeddingAPI: Catching too general exception Exception
C:604,22:packEmbeddingAPI: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:581,5:packEmbeddingAPI: Unused variable 'return_code'
R:551,0:packEmbeddingAPI: Too many return statements (15/6)
R:551,0:packEmbeddingAPI: Too many branches (18/12)
C:638,0:packAPP: Invalid name "packAPP" (should match [a-z_][a-z0-9_]{2,30}$)
C:638,0:packAPP: Missing docstring
W:643,15:packAPP: Catching too general exception Exception
C:643,26:packAPP: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
R:638,0:packAPP: Too many return statements (8/6)
R:638,0:packAPP: Too many branches (13/12)
C:670,0:createIndexFile: Invalid name "createIndexFile" (should match [a-z_][a-z0-9_]{2,30}$)
C:670,0:createIndexFile: Missing docstring
W:680,11:createIndexFile: Catching too general exception Exception
C:680,22:createIndexFile: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
C:687,0:buildSubAPP: Invalid name "buildSubAPP" (should match [a-z_][a-z0-9_]{2,30}$)
C:687,0:buildSubAPP: Missing docstring
C:720,0:buildPKGAPP: Invalid name "buildPKGAPP" (should match [a-z_][a-z0-9_]{2,30}$)
C:720,0:buildPKGAPP: Missing docstring
R:720,0:buildPKGAPP: Too many return statements (8/6)
R:720,0:buildPKGAPP: Too many branches (14/12)
C:758,0:buildPKG: Invalid name "buildPKG" (should match [a-z_][a-z0-9_]{2,30}$)
C:758,0:buildPKG: Missing docstring
C:777,0:main: Missing docstring
R:777,0:main: Too many local variables (23/15)
W:778,4:main: Using the global statement
W:814,11:main: Catching too general exception Exception
W:812,8:main: Using the global statement
C:814,22:main: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:848,11:main: Catching too general exception Exception
C:848,22:main: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:898,11:main: Catching too general exception Exception
C:898,22:main: Invalid name "e" (should match [a-z_][a-z0-9_]{2,30}$)
W:902,4:main: Using the global statement
W:813,27:main: Unused variable 'args'
R:777,0:main: Too many branches (39/12)
R:777,0:main: Too many statements (129/50)
W: 42,0: Unused import make_option


Report
======
705 statements analysed.

Raw metrics
-----------

+----------+-------+------+---------+-----------+
|type      |number |%     |previous |difference |
+==========+=======+======+=========+===========+
|code      |754    |90.73 |754      |=          |
+----------+-------+------+---------+-----------+
|docstring |17     |2.05  |17       |=          |
+----------+-------+------+---------+-----------+
|comment   |29     |3.49  |29       |=          |
+----------+-------+------+---------+-----------+
|empty     |31     |3.73  |31       |=          |
+----------+-------+------+---------+-----------+



Statistics by type
------------------

+---------+-------+-----------+-----------+------------+---------+
|type     |number |old number |difference |%documented |%badname |
+=========+=======+===========+===========+============+=========+
|module   |1      |1          |=          |0.00        |0.00     |
+---------+-------+-----------+-----------+------------+---------+
|class    |1      |1          |=          |0.00        |0.00     |
+---------+-------+-----------+-----------+------------+---------+
|method   |2      |2          |=          |100.00      |0.00     |
+---------+-------+-----------+-----------+------------+---------+
|function |28     |28         |=          |0.00        |96.43    |
+---------+-------+-----------+-----------+------------+---------+



Messages by category
--------------------

+-----------+-------+---------+-----------+
|type       |number |previous |difference |
+===========+=======+=========+===========+
|convention |125    |125      |=          |
+-----------+-------+---------+-----------+
|refactor   |13     |13       |=          |
+-----------+-------+---------+-----------+
|warning    |31     |31       |=          |
+-----------+-------+---------+-----------+
|error      |3      |3        |=          |
+-----------+-------+---------+-----------+



Messages
--------

+-----------+------------+
|message id |occurrences |
+===========+============+
|C0301      |55          |
+-----------+------------+
|C0103      |40          |
+-----------+------------+
|C0111      |30          |
+-----------+------------+
|W0703      |11          |
+-----------+------------+
|W0603      |10          |
+-----------+------------+
|W0612      |6           |
+-----------+------------+
|R0912      |5           |
+-----------+------------+
|R0911      |5           |
+-----------+------------+
|R0914      |2           |
+-----------+------------+
|E1101      |2           |
+-----------+------------+
|W0702      |1           |
+-----------+------------+
|W0622      |1           |
+-----------+------------+
|W0613      |1           |
+-----------+------------+
|W0611      |1           |
+-----------+------------+
|R0915      |1           |
+-----------+------------+
|E0602      |1           |
+-----------+------------+



Global evaluation
-----------------
Your code has been rated at 7.39/10 (previous run: 7.39/10)

Duplication
-----------

+-------------------------+------+---------+-----------+
|                         |now   |previous |difference |
+=========================+======+=========+===========+
|nb duplicated lines      |0     |0        |=          |
+-------------------------+------+---------+-----------+
|percent duplicated lines |0.000 |0.000    |=          |
+-------------------------+------+---------+-----------+

Enable CI Status on Pull Requests

https://github.com/w3c/web-platform-tests has enabled https://travis-ci.org/w3c/web-platform-tests to automatically check every pull request. This is a good practice. Let's enable this continuous integration service here.

Some references:

• https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.md#ci-status-on-pull-requests
• https://github.com/blog/1227-commit-status-api
• https://developer.github.com/v3/repos/statuses/

XWalkViewWithScrollViewParentAsync is not working

running XWalkViewWithScrollViewParentAsync shows nothing on beta:18.48.477.6

[webapi] Combine `support/user.js` and `support/cssstyle.js`

When review #552, I find there are 2 support files with same APIs for CSS testing:

• tct-animations-css3-tests/animations/support/user.js
• tct-multicolumn-css3-tests/multicolumn/support/user.js
• tct-text-css3-tests/text/support/user.js
• tct-transitions-css3-tests/transitions/support/user.js
• tct-ui-css3-tests/ui/support/user.js
• tct-backgrounds-css3-tests/backgrounds/support/cssstyle.js
• tct-colors-css3-tests/colors/support/cssstyle.js
• tct-multicolumn-css3-tests/multicolumn/support/cssstyle.js
• tct-ui-css3-tests/ui/support/cssstyle.js

We'd better combine them and maintain only one support file (each test suite has the same copy).

Personally, I prefer support/support.js to support/user.js and support/cssstyle.js.

Please @Honry and @JianfengXu take care of this issue, thanks.

XWALK-2233 Add test case for Cordova Screenshot plugin

When using Screenshot Cordova plugin to capture screenshot of xwalkView, it always capture BLACK screen. When switching back to the normal Andriod webview, it can capture the screen successfully.
For more details, please check https://crosswalk-project.org/jira/browse/XWALK-2233

Web SQL Transfer Support?

I see many references in the test code for Web SQL alongside localStorage and IndexDB in regards to validating that crosswalk can work well after upgrading using higher Crosswalk binary and runtime library.

Mainly unsure because the tests are commented out here: https://github.com/crosswalk-project/crosswalk-test-suite/blob/master/usecase/usecase-cordova-android-tests/samples/Database/res/database_source/js/main.js, and that it is not mentioned here: https://crosswalk-project.org/blog/crosswalk-15-beta.html

I was hoping to just verify, is Web SQL also migrated when upgrading a non-Crosswalk app to use Crosswalk?

This may have been an issue/question suited for another repo, but all of my initial investigating pointed to more references here.

Thank you.

Bug with many XwalView in activity (in fragments)

I write simple project using XWalkView
https://github.com/kenumir/XWalkViewFragmentTest

When open more than one fragment with XWalkView view on background shows all the time first page, touch event is not working (new fragment ovelay with transparency page in background).

Everything is ok when use replace instead of add when fragment is created.
It looks like only one XWalkView can be used on activity?

Any solution of this problem?

XWALK-2188 Add onshow(), onhide() test cases for XWalkView

XWALK-2188 [Android] XWalkView will display a short white screen when press home button
[Belem] QA didn't find this issue. Do we need add this test scenario?
[Cao, Jenny Q] onshow(), onhide() is not published embedding API， so would not covered in embedding API test.
Need add a system test for this senario.

Refactor package installation scripts in Python

Background

At #753 (comment), I found that most of the inst.*.py files have the same line of code.

• webapi/tct-2dtransforms-css3-tests/inst.apk.py (107)
• webapi/tct-2dtransforms-css3-tests/inst.wgt.py (207)
• webapi/tct-2dtransforms-css3-tests/inst.xpk.py (208)
• webapi/tct-2dtransforms-css3-tests/suite.json (54)

At current being, there are 606 inst.*.py files in this repository, which contain lots of duplicates.

Proposal

Redesign these installing scripts and keep one of the copies into tools/build/ accompanying with tools/build/pack.py.

Known Issue

As @yugang pointed out, WRT test suites have specific requirements suite-by-suite. It is not easy to unify the installation scripts.

The first step can be started from WebAPI part.

Refactor scripts of test framework, support resources and web runner

Background

In this test repository, we create test cases based on W3C testharness.js framework, Samsung unitcommon.js, and run the test cases based on Intel webrunner.

At current being, these scripts are located in each test suite for historical reason. Thus make them lots of copies. See detail analysis here.

Proposal

• Create resources/ in the root of this repository to hold below scripts. Here doesn't use sub-module because we can put all support resources into this directory. List the script files and number of copies here.
  • testharness.css (224)
  • testharness.js (224)
  • testharnessreport.js (223)
  • unitcommon.js (49)
  • jquery.js (6)
  • jquery-1.10.2.min.js (220)
  • jquery.min.js (3)
  • jquery.mobile.js (6)
  • jqueryprogressbar.js (2)
  • slider.tooltip.js (11) see also #866
  • testcase.xsl (197)
  • testresult.xsl (169)
  • tests.css (201)
• Make webrunner sub-module for webrunner in the root of this repository
  • Please note that this contains jquery-1.10.2.min.js too.
  • testrunner.js (220)

To easy the test suite packaging, create a script tools/build/copy.py to copy the scripts above to current being placeholder.

XWALK-2169 Add test case for PDFjs usage

XWALK-2169 Can't open pdf via PDFjs which loads into crosswal view. Logs shows issues with opengl
[Belem] http://mozilla.github.io/pdf.js/ a web standards-based platform for parsing and rendering PDFs. We may need test case for it.
[Cici] Add a test case in misc/system

Get rid of packaging scripts in Shell

Near 3 weeks ago, we created packaging scripts in Python to support multiple platforms at #748. It is time to get rid of the packaging scripts in Shell. This issue report is trying to remove below files from this repository. Please note that I will remove them directly (without pull request) by command find . -name '<filename>' -type f | xargs git rm -f if no objection in this week.

• autogen
• configure.ac
• inst.sh.apk
• inst.sh.tct.wgt
• inst.sh.wgt
• inst.sh.xpk
• Makefile.am
• pack.sh
• *.spec