Core Tests - qooxdoo $(qxversion)

Tool Chain Tests - Grunt & Generator

Reminder: Run tests via grunt frontend ('grunt source' vs. 'generate.py source')

1	Source/Build	Job (Platform: Python: Node.js:)
1	Source/Build	source^[a]	source-all^[a]	source-hybrid^[a]	build^[a]
1.1	Desktop skeleton
1.2	Inline skeleton
1.3	Native skeleton
1.4	Website skeleton ^[c]	N/A	N/A	N/A	^[d]
1.5	Server skeleton		N/A	N/A
1.6	Mobile skeleton

2	GUI Tools	Job (Platform: Python: Node.js:)
2	GUI Tools	api^[a]	api-data
2.1	Desktop skeleton
2.2	Inline skeleton
2.3	Native skeleton
2.4	Website skeleton
2.5	Server skeleton
2.6	Mobile skeleton

3	Test	Job (Platform: Python: Node.js:)
3	Test	test^[a]	test-source^[a]	test-mobile^[a]
3.1	Desktop skeleton			N/A
3.2	Inline skeleton			N/A
3.3	Native skeleton			N/A
3.4	Website skeleton			N/A
3.5	Server skeleton			N/A
3.6	Mobile skeleton

4	Code Maintenance	Job (Platform: Python: Node.js:)
4	Code Maintenance	lint^[a]	fix^[a]	pretty^[b]	translation^[a]
4.1	Desktop skeleton
4.2	Inline skeleton
4.3	Native skeleton
4.5	Server skeleton
4.6	Mobile skeleton

5	Shell Tools	Job (Platform: Python: Node.js:)
5	Shell Tools	watch^[a]	source-server^[a]	source-server-reload^[a]	source-httpd-config^[a]	validate-config	validate-manifest	clean	info
5.1	Desktop skeleton
5.2	Inline skeleton
5.3	Native skeleton
5.4	Website skeleton ^[c]	N/A	N/A	N/A	N/A		N/A
5.5	Server skeleton		N/A	N/A	N/A
5.6	Mobile skeleton

6	Migration	Job (Platform: Python: Node.js:)
6	Migration	migration^[e]
6.1	Desktop skeleton

Documentation Tests
7	Manual
7.1	Check index.html (general layout, topic listing)
7.2	Check a few content pages (general layout)
7.3	Check breadcrumbs
7.4	Try the Search tool (number of hits, display of search results)
7.5	PDF (don't use index.html link, but qooxdoo.pdf; should be around 500-600 pages)

Legend:
Ok
() Mainly Ok
Not Ok

Annotations

General

The main objective of these tests is to make sure the generator jobs run through, and produce applications that load ok in the browser.

[a]

The console output should contain no warnings.

[b]

To verify pretty-printing, look at some code (e.g. Application.js, DemoTest.js) including its comments, just enough to make sure it is not wildly misformatted. (Don't count indent levels or ponder about opening curlies). Then run a subsequent source job, to make sure it still compiles.

[c]

Without any generation, open the local index.html. The demo should run immediately.

[d]

The job to run is build (or just generate.py without a job). It will re-create the Website library into the script/ folder. Reload the index.html to ensure it is working.

[e]

Simple migration test:
- create a skeleton application from a previous release
- create a corresponding skeleton from the current release
- delete the source/class folder from the current skeleton
- copy over the source/class folder from the previous skeleton
- run generate.py migration
Advanced migration test:
- copy the Feedreader application of a previous release
- edit config.json/QOOXDOO_PATH to point to the qooxdoo installation under test
- run generate.py migration

In both cases, the migration job should terminate normally, with various log messages on the console. During migration you should be offered to enter your "old" qooxdoo version, a suitable upgrade path leading up to the version under test should be printed out. After the migration, a file migration.log should be created that contains the per-version, per-file entries, deprecation warnings and modification statements. After that, a generate.py source may or may not terminate normally, and the created application, if any, may or may not run in the browser.