wptt / theme-test-data Goto Github PK

View Code? Open in Web Editor NEW

This project forked from garyjones/theme-unit-test

622.0 36.0 16.0 37.92 MB

Theme Test Data

theme-test-data's Introduction

Theme Test Data -Formerly Theme Unit Test

For instructions on how to use the Theme Test Data please see https://codex.wordpress.org/Theme_Unit_Test

To download the Accessibility teams test file, please go to: https://github.com/wpaccessibility/a11y-theme-unit-test

Workflow

Note that issues and pull requests for the theme preview file will not be reflected on WordPress.org. This file is for testing only.

If you find a problem with the theme unit test: go here https://github.com/WPTT/theme-test-data/issues and see if an issue has been opened for this problem. If not, open an issue.

To help solve an issue: fork the repository, create a branch for the update, and make a pull request. Make sure that you check the box allowing others to make edits.

To review a pull request: view it and/or test it locally and add your comments.

If a pull request is ready to be merged and this has been noted already in a review but you do not have permission to merge, then be patient. 🙂 If the pull request that is ready to be merged has not been merged for some time, ping @pattonwebz on the issue.

After merging, go to this codex page, https://codex.wordpress.org/Theme_Unit_Test, log in, and update the last updated date.

theme-test-data's People

Contributors

Stargazers

Watchers

Forkers

andronocean rr-yumi radiusrobbani valzya akozoubsky casa-de-bob arfinmilondev theiphoner abuhorairatarif flexseth imagedirect tanvirulhaque nababur jays72phome sabbir-noyon razon-xs

theme-test-data's Issues

new import, shows errors

Did an import with the current .xml into a WP 4.9.4 site. Got the following errors:

Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Notice: Undefined offset: 1 in /wp-content/plugins/wordpress-importer/parsers.php on line 467
Failed to import Page "Lorem Ipsum"
Failed to import Post "Post Format: Aside"
Failed to import Page "Page Markup And Formatting"
Failed to import Post "Markup: HTML Tags and Formatting"

WXR error

So downloading the latest from this repo and importing into my WordPress installation results in

This does not appear to be a WXR file, missing/invalid WXR version number.

The old version from 2015 Oct works ;/

'Block: Button' not using latest button structure

The buttons blocks on the "Block: Button" post is out dated and should be wrapped inside of the .wp-buttons wrapper. If theme developers use this class, the theme may appear to have bugs.

character entities instead of brackets

The < and > need to be the real < and > characters here.

https://github.com/WPTRT/theme-unit-test/blob/d6301641f02b278f4a527b2cb0a0ad092f2322fe/themeunittestdata.wordpress.xml#L9725

Alt Text is duplicated for each image

Each image's alt text is duplicated, which causes mysql errors after import (subqueries returning more than 1 row).

For example:

wp:postmeta
wp:meta_key_wp_attachment_image_alt</wp:meta_key>
wp:meta_value</wp:meta_value>
</wp:postmeta>
wp:postmeta
wp:meta_key_wp_attachment_image_alt</wp:meta_key>
wp:meta_value</wp:meta_value>
</wp:postmeta>

fileSize too big

I don't know if this is the right place to post this. Please correct me if I am wrong.
I am trying to import the Theme_Unit_test into Wordpress and it tells me that the file is too big. Any ideas would be greatly appreciated. Thank you.
P.S. I am using a localhost.
Cheers!

"Import WordPress

Sorry, there has been an error.
The uploaded file exceeds the upload_max_filesize directive in php.ini."

File size is over 3 MB and the limit is 2 MB

Fixed: add line to .htaccess file =

php_value upload_max_filesize 10M
php_value post_max_size 10M
LimitRequestBody 0

Hope that helps someone else looking for the same answer.

Add tests for editor blocks (Gutenberg)

We need to add examples of editor blocks so that theme authors can test them easily.

I will include this link as an example:
https://github.com/thatplugincompany/block-unit-test

Comment author IP needs to be removed

The comment author IP is stored in the xml file, I don't believe that is in accordance with GDPR, neither storing or sharing it.
The ip needs to be removed from existing comments and from any future comments that we may want to add.

Revise existing users

Do we need any users other than themedemos?
The menu items and images from Chip, Emil and Lance can be transferred over to the themedemos user.

If we need the users for anything else, the personal e-mails should probably be replaced.

Scheduled Post Date Needs to Be Set for a Future Date

Theme Unit XML File has a post that is supposed to appear as a scheduled post with a date set in future. Originally it was set to January 01, 2020. That date has now passed.

Please fix this and set a date in the future
https://github.com/WPTT/theme-unit-test/blob/d12c67cddad161360c88e4df45205b3eded8c93e/themeunittestdata.wordpress.xml#L8673

New WordPress 6.1 content is created as Posts, not Pages

I initially couldn't mind the newly-updated posts that contain blocks. I think these should be included as Pages so they are all together.

I'd propose the import be updated to import all unit test content as Pages.

Deciding unit test version and syncing.

As mentioned on slack, we might need to reconsider which version of the unit test we should work with, and establish what our goal is here.

See
https://codex.wordpress.org/Theme_Unit_Test
which links to a version maintained by automattic:
https://wpcom-themes.svn.automattic.com/demo/theme-unit-test-data.xml

On this page there are two other versions. -I have not compared these versions.
https://wpcom-themes.svn.automattic.com/demo/
one called demo-data.xml, and one for .com: wordpress-com-theme-test.xml

Do we create our own version, or should we sync with automattic's version (If this is even possible)?
Should we perhaps sync with the .org theme previewer, or do we keep these as two separate projects?.
Do we want to be in charge of keeping the codex page up to date, or do we prefer to separate the
current theme unit test and the "theme review unit test" ?

Menu problems

I imported into a new site, and the All Pages Flat menu was empty. The Testing menu had duplicate entries for Page Image Alignment and Page Markup And Formatting.

International content

After conversations with various theme developers who work with other languages than English, it occurred to me the Theme Unit Test Data could benefit greatly from having proper international content. This would allow testing of things like long words (Finnish, Icelandic, Inuktitut, etc), non-english letters in their natural context (eg æ, ø, å, germanic ß, various accents, etc), RTL languages, and the likes.

Right now, the only way to test a theme for support of non-english letters is through the character map, but this doesn't provide a good testing scenario. Likewise, RTL testing can be done using a plugin, but it'll be applied to English content, not actual RTL languages.

Having a couple of posts in representative languages - Finnish, German, French, Spanish, Simplified Chinese, Farsi, Hebrew, etc - would make it easier for theme developers to test their themes not only against English, but other real language examples.

Convert existing content to blocks

The current content is displayed in a Classic block. We should convert it to blocks.

There should be no visual difference thanks to backwards compatilibity.

Changing the name of this repo to "Theme Acceptance Test" instead of "Theme Unit Test"

This is a proposal to change the name of this repository for better reflect what it does because this is more a user front-end test and not a unit test -> https://en.wikipedia.org/wiki/Acceptance_testing

I know the file is as a decade old but when I read unit test this confusing me and the risk of feeding wrong terminologies in young developers is high.

.bypostauthor class is not added to comments

I have the problem, that the ".bypostauthor" Class is not added to the comments of "themedemos" in the comments template post. I have changed the Name of the Themedemos User to test if the name of the comments changes. But it does not.

incorrect date on wordpress codex

https://codex.wordpress.org/Theme_Unit_Test

Says that theme unit test file was last updated on 1st May 2019 (not march).

Please update it. Looks highly unprofessional this way.

Use different size images for testing alignments

I never thought it would happen, but someone wrote a theme with CSS specific to the unit test data, which makes the image alignment pages look okay even though the standard WP classes were not defined.
https://themes.trac.wordpress.org/ticket/71793#comment:3

Remove the CSS that is specific to the unit test data:

.content-page .alignleft{ width: 150px;}
.content-page .alignright{ width: 300px;}
.content-page .aligncenter{ width: 580px;}
.post-content .alignright{ width: 300px;}
.post-content .aligncenter{ width: 580px;}
.post-content .alignleft{ width: 150px;}

It would also be good to test large images aligned left or right, and large captioned images centered.

When using test data block validation error in console for Block Gallery post

Please follow these steps

Import WordPress test data from Theme unit test data page
Edit "Block: Gallery" post
Right click and Inspect element
Go to console
Can see this error
Block validation: Block validation failed for core/spacer ({name: "core/spacer", title: "Spacer", description: "Add white space between blocks and customize its height.", icon: {…}, category: "layout", …}).

Jet Pack Tests

There are special tests in Theme Unit Test for Tiled Gallery and VideoPress.

As far as I can tell these JetPack plugins were moved to JetPack Pro?

If that is the case then these tests should be removed.

Add license information for the media content

Add information about license and source for the media content.
This was recently requested in the #themereview WordPress Slack channel and is needed when theme authors intend to use the images in screenshots etc.

If information can not be found consider replacing the images.

wptest.io image links broken

Example: themeunittestdata.wodpress.xml:1494

http://wptest.io/demo/wp-content/uploads/2011/01/dsc20050727_091048_222.jpg

Post updated date is not tested

Currently the post entry meta tests only creation date and not updated date.

Like: "Posted on March 14, 2012" and not "Posted on March 14, 2012 and updated on March 21, 2012".
Maybe this is an useful scenario ...

If you think I can add this feature.

Old markup is creating JS errors in the site editor

Old block markup in the theme unit test file is creating JavaScript errors in the site editor because the markup is invalid.

We may need to reconsider keeping the old markup in the file, or having different versions of the file for different WordPress versions.

Use "Heading" in place of "Header" when technically accurate

Since the WordPress interface correctly uses "Heading" for h1, h2, etc. the theme unit test content should also use "Heading". In many cases, it currently uses "Header" which can mean a page region or type of content, either semantic (the <header> element) or generic.

"Antidisestablishmentarianism" is too short a title to meaningfully test overflow.

How about the long form of Llanfairpwllgwyngyll:
Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch

Alternately, https://en.wikipedia.org/wiki/Taumatawhakatangihangakoauauotamateaturipukakapikimaungahoronukupokaiwhenuakitanatahu

WXR file format for Playground

Can we host a WXR file format in this GitHub repo to use for importing to WP Playground installs?

Revise links

The theme review link leads to http://codex.wordpress.org/Theme_Review
this needs to be updated.

Check for and update 404's.
Do we keep the references to http://wptest.io/? apple.com?

Block: Button post still shows Rounded option

The Block Button post still shows the rounded button option, but this button style was removed here. Should this test data be updated to remove the Rounded style since it no longer exists?

WP 6.1 Font size scale post has wrong heading size

In the "WP 6.1 Font size scale" post, the Extra Large H2 Heading is incorrectly set to "fontSize":"large".

// line 1109
<!-- wp:heading {"fontSize":"large"} -->
<h2 class="wp-block-heading has-large-font-size">Extra Large H2 Heading</h2>
<!-- /wp:heading -->

Title With Markup does not have markup.

To be able to test this, the title needs to have markup.
<title>Markup: Title With Markup</title>
should be
<title>Markup: Title <em>With</em> <b>Markup</b></title>

Update the existing blocks to newer syntax

Gutenberg has changed some of the syntax of the blocks, such as quote blocks and anything that had text alignment (it was inline style, and is now a class).
See https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/

"This block contains unexpected or invalid content"

I see this in the latest release of theme-test-unit:

due, it seems, to this:

Tested with Twenty-Nineteen as well.

Update https://wpthemetestdata.wordpress.com/

There is content that is in the xml file that doesn't exist on the actual page, which can be unexpected.

Convert classic content to Gutenberg block

I wonder if we should update the test data to Gutenberg blocks, or at least to create a version specifically converted in blocks?
If this can help or if interested at all, I could provide a converted version of the classic content into Gutenberg blocks.

Invalid time on one of the posts in exported XML

One of the posts in export file has invalid time of 19:57:357

https://github.com/WPTRT/theme-unit-test/blob/8754eade34b536788214f89567ff62759d106de6/themeunittestdata.wordpress.xml#L3870

No idea how it ended up like that, using the file as test data and my code trips up on this.

The link you followed has expired.

Every time I tried to import its through The link you followed has expired.

Identify and remove unnecessary tags

We should identify and remove unnecessary tags,
tags that have been created on export, that are not imported by the current WordPress importer and /or are not used.

Missing ids of gallery images

There is missing ids of images used in gallery shortcode and return of get_post_gallery() function doesn’t contain ids key => value pair.

Ids list appears in shortcode after updating gallery in editor

This does not appear to be a WXR file?

Import WordPress

Sorry, there has been an error.
This does not appear to be a WXR file, missing/invalid WXR version number

Fresh install, first thing I did was go to import the theme unit test data and got this message. Can anyone explain what this means or what I may need to do to fix this?

New content suggestions

-A Note that the Theme Unit test is recommended for theme reviews, not required.
-Add a test for keyboard navigation.
-A social menu

Time to update theme test data?

Please consider updating the theme-test-data to completely display every WordPress 5.9 Gutenberg block.

Testing Title Overflow

For many themes, this "test" doesn't test anything as the text is not long enough to overflow its container:

I'd recommend at least double the current characters to properly test most themes.

Missing content in two titles

Seems to me the post: "Title with markup"
misses the markup in the title, probably due to conflicting PRs.

Also, the post "Title with special characters"
misses the special characters.

Make some top level menu links actual links

The menus need to have top level links that go to content. I keep finding themes that change top level links to #. I assume it's because the test data does not have actual top level links, so authors don't realize that they can be.
Maybe the link could say it's a link or somehow mention what to check for somewhere.