Testing

This morning I experimented with some Google searches which can reveal information on public sites.

Inspired by some posts from @Random_Robbie on Twitter

These are now know as Google Dorks.

TLDR; If you self-host a Wordpress site, make sure you can restore from backups and check your site using wpscan and other tools regularly.

TLDR; Some games are not meant to be played, they are meant to be played with.

I recently released “Protect The Square”, which according to my version control system I wrote on 2nd May 2016. I had forgotten about it.

I found it again a few days ago and decided to release it as the technical exploration exercise it was intended for.

TLDR; Reverse counterstrings are easier to generate. Creating same output forward is harder but might be useful for streaming or files.

TLDR; Too many scope and reporting restrictions on testing attenuates both noise and signal.

TLDR; Turnkey linux VM for testing Tracks using network settings Bridged, or Host Only.

I normally use VM Ware, but I create a video showing Turnkey Linux and Virtual Box to help people with the network settings.

TLDR; I can view Problem Solving as Problem Identification, Problem Solution Construction, Solution Evaluation and I can map that on to Software Development to help me communicate in normal language.

TLDR; Testers often find bugs in production systems. But with no incentive to raise them we find workarounds and they go unreported.

TLDR; I can fool myself into comfortable complacency about code when programming. I can use testing to banish this false glamor.

TLDR; Learning to use browser dev tools can help you investigate defects that have no visible output on the Web GUI, and they can help you bypass problems in the real world.

One common bug that I find a lot with web applications are errors that do not get reported to the user.