Skip to main content

Random text tool

I recently blogged about some of the tools I use, and how some are so useful I keep using them. As I mentioned, randomness is pretty useful, and I have tools to help me generate random text.

A few of my readers requested a copy of my simple random text generating script, so I've decided to open it up for everyone to use and test. It will have bugs, like all software, please send details and I'll try and fix them.

If you are interested in what UTF-8 is and what all that Unicode stuff is about, there is a great article by Joel Spolsky that explains all, and the wikipedia page is ok.

To use it...

First download the script, its on GitHub. The script is fairly short and is all in one file. You don't have to 'install it', its not a GEM.

Second, make sure you have Ruby version 1.9 or greater. You need version 1.9, because Ruby didn't handle UTF-8 well in older versions.

Thirdly run the script like this:

ruby fuzzutf8.rb

That will give you some usage examples.

Typically you might use it like this:

ruby fuzzutf8.rb -c 100 -utf8_two_byte
ծݸԒ̂ƍՔ͌вЊޏΒđµʠ£أҋ‘ŷݟߢ؁ˬУԝψĭ͕ѼХׅ۲ѨÃːׁǡ ܮ͂ϗՎœߔƭ̷Ȼ̧ʕʏٔǝ͈ܰȄبǚŎڿξަدʓ׽߷ЊݑڷũɛӥѤ̸ôߋȭԭæúѫܚʽͫʔƦܾ߷Ûƕͱ՛عӯ̨֢د߻Ӈ

That's a hundred code-points of UTF-8, in the two byte range.

As operating systems sometimes have issues copying and pasting these code-points (e.g. Windows XP) You may prefer to redirect the contents straight to a text file. e.g.:

ruby fuzzutf8.rb -c 100 -utf8_two_byte > random_utf8_file.txt

You can then treat the output like any other file. You can open it in a text editor, but beware many programs can not handle random UTF8 well, You may wish to save your work first.

The script also allows you to keep a record of the code-point numbers generated in a separate file ( -o option). These can then be replayed at a later date should you need to ( -r option ). The script doesn't do a lot of validation, so you can probably have great fun tripping the script itself up with dodgy inputs and arguments ;-)

I'm confident the script has many bugs, but it is nonetheless quite useful, and has been useful in helping me to locate other bugs. If you are interested in random text generators, There is a windows tool that I've also found useful, called Babel from TestMentor. Babel allows you to choose the output by character set/codepoint range, which is also interesting.

Comments

Popular posts from this blog

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship” “Are you willing to bet on that?” No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten. Instead, I recommend you to ask yourself that question next time you believe you are finished.  Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach. Testing is gambling with your time to find information about the app. Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app

Test Engineers, counsel for... all of the above!

Sometimes people discuss test engineers and QA as if they were a sort of police force, patrolling the streets of code looking for offences and offenders. While I can see the parallels, the investigation, checking the veracity of claims and a belief that we are making things safer. The simile soon falls down. But testers are not on the other side of the problem, we work alongside core developers, we often write code and follow all the same procedures (pull requests, planning, requirements analysis etc) they do. We also have the same goals, the delivery of working software that fulfills the team’s/company's goals and avoids harm. "A few good men" a great courtroom drama, all about finding the truth. Software quality, whatever that means for you and your company is helped by Test Engineers. Test Engineers approach the problem from another vantage point. We are the lawyers (& their investigators) in the court-room, sifting the evidence, questioning the facts and viewing t

XSS and Open Redirect on Telegraph.co.uk Authentication pages

I recently found a couple of security issues with the Telegraph.co.uk website. The site contained an Open redirect as well as an XSS vulnerability. These issues were in the authentication section of the website, https://auth.telegraph.co.uk/ . The flaws could provide an easy means to phish customer details and passwords from unsuspecting users. I informed the telegraph's technical management, as part of a responsible disclosure process. The telegraph management forwarded the issue report and thanked me the same day. (12th May 2014) The fix went live between the 11th and 14th of July, 2 months after the issue was reported. The details: The code served via auth.telegraph.co.uk appeared to have 2 vulnerabilities, an open redirect and a reflected Cross Site Scripting (XSS) vulnerability. Both types of vulnerabilty are in the OWASP Top 10 and can be used to manipulate and phish users of a website. As well has potentially hijack a user's session. Compromised URLs, that exp