Dan Smith dotherightthing

Unit testing: PHPUnit + Cypress

I've been testing my gallery plugin using local and remote URLs.

This seemed reasonable until I realised that it breaks the release process.

This is because the release needs to test an updated environment, but the environment is only updated by the release. So my tests would pass on local dev, but fail when run through the CI, which could only see the remote URL.

Note: I just remembered that there's actually a way to expose a local URL to other internet users, I didn't try this.

Unit Testing: Handling dependencies

I'm already familiar with unit testing, but there are gaps in my knowledge.

I like to test real code, so I have been trying to test some of my custom Gulp modules.

Problem 1: Can't test modules with dependencies

Module:

Using Postman to test Google Docs API

1. Get credentials from Google

Using OAuth 2.0 to Access Google APIs > Basic steps

Visit the Google API Console to obtain OAuth 2.0 credentials such as a client ID and client secret that are known to both Google and your application.

Credentials > Create credentials > OAuth client ID > Other
Close the window containing your Client ID and Client Secret
In the Credentials list, click on the name of the new OAuth 2.0 client ID
Click DOWNLOAD JSON

&shy;

WordPress SEO

Meta descriptions

(Yoast) SEO
Search Appearance
Content Types
[Content Type]
Meta description
Insert snippet variable

Post meta vs separate database tables

An interesting read from Post meta vs separate database tables

If your plugin is going to have A LOT of data, then using the wp_postmeta is NOT a good idea as demonstrated below:

Taking Woocommerce as an example,

In a store with ~30,000 products, say there will be an average of ~40 post meta (attributes and everything) per product, 5 product images per product, which means there will be ~4 image meta for each image:

Check whether a string contains invisible characters

json_encode($string)

Source: SO: Cannot get array element by key, but key exists on array

Type declarations

AKA Type hinting.

Background

I used to use phpDocumentor. It had this nice feature where you could document:

the type of input that was expected
the type of output that was expected

Remove incorrect authentication password from Composer config

Background

Whilst migrating my Yeoman dependency install to a bash script (that I could also run later), I inadvertently set my Github OAuth password to the string "process.env.GH_TOKEN".

Error

[UnexpectedValueException]

	/**
	* Function: camelCaseToSentence
	*
	* Parameters:
	* string - An UpperCamelCase or lowerCamelCase string
	*
	* Returns:
	* A sentence string
	* _____________________________________
	*/