88Probet is the most trusted account management tool in Asia. It is the ultimate destination for Craps Cheat Sheet everyone who wants a complete sports experience.
- SQL Cheat Sheet: SQL (Structured Query Language) is a special-purpose programming language that’s widely used for managing data stored in relational databases. SQL was initially developed at IBM.
- Software Engineer Cheat Sheet. About the author. Sarah Cooper is an author and speaker. Her first book, 100 Tricks to Appear Smart.
- This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon. The Technical Interview Cheat Sheet.md.
- For full instructions on advanced searching in JIRA Software, please visit: Replace single character with?
In a previous post, I described how I was captivated by the virtual landscape imagined by the RStudio education team while looking for resources on the RStudio website. In this post, I’ll take a look atCheatsheets another amazing resource hiding in plain sight.
Apparently, some time ago when I wasn’t paying much attention, cheat sheets evolved from the home made study notes of students with highly refined visual cognitive skills, but a relatively poor grasp of algebra or history or whatever to an essential software learning tool. I don’t know how this happened in general, but master cheat sheet artist Garrett Grolemund has passed along some of the lore of the cheat sheet at RStudio. Garrett writes:
One day I put two and two together and realized that our Winston Chang, who I had known for a couple of years, was the same “W Chang” that made the LaTex cheatsheet that I’d used throughout grad school. It inspired me to do something similarly useful, so I tried my hand at making a cheatsheet for Winston and Joe’s Shiny package. The Shiny cheatsheet ended up being the first of many. A funny thing about the first cheatsheet is that I was working next to Hadley at a co-working space when I made it. In the time it took me to put together the cheatsheet, he wrote the entire first version of the tidyr package from scratch. Ksp geostationary orbit over ksc.
It is now hard to imagine getting by without cheat sheets. It seems as if they are becoming expected adjunct to the documentation. But, as Garret explains in the README for the cheat sheets GitHub repository, they are not documentation!
RStudio cheat sheets are not meant to be text or documentation! They are scannable visual aids that use layout and visual mnemonics to help people zoom to the functions they need. … Cheat sheets fall squarely on the human-facing side of software design.
Cheat sheets live in the space where human factors engineering gets a boost from artistic design. If R packages were airplanes then pilots would want cheat sheets to help them master the controls.
The RStudio site contains sixteen RStudio produced cheat sheets and nearly forty contributed efforts, some of which are displayed in the graphic above. The Data Transformation cheat sheet is a classic example of a straightforward mnemonic tool.It is likely that even someone who just beginning to work with
dplyr
will immediately grok that it organizes functions that manipulate tidy data. The cognitive load then is to remember how functions are grouped by task. The cheat sheet offers a canonical set of classes: “manipulate cases”, “manipulate variables” etc. to facilitate the process. Users that work with dplyr
on a regular basis will probably just need to glance at the cheat sheet after a relatively short time.The Shiny cheat sheet is little more ambitious. It works on multiple levels and goes beyond categories to also suggest process and workflow.
The Apply functions cheat sheet takes on an even more difficult task. For most of us, internally visualizing multi-level data structures is difficult enough, imaging how data elements flow under transformations is a serious cognitive load. I for one, really appreciate the help.
Cheat sheets are immensely popular. And even in this ebook age where nearly everything you can look at is online, and conference attending digital natives travel light, the cheat sheets as artifacts retain considerable appeal. Not only are they useful tools and geek art (Take a look at cartography) for decorating a workplace, my guess is that they are perceived as runes of power enabling the cognoscenti to grasp essential knowledge and project it in the world.
Cheat Sheet Generator
When in-person conferences resume again, I fully expect the heavy paper copies to disappear soon after we put them out at the RStudio booth.
I came across Elisabeth Hendrickson's 'Test Heuristics Cheat Sheet' yesterday and developed some pairwise testing (AKA 2-way combinatorial) test cases using many of the good ideas contained in it. I would highly recommend it, I'd recommend you send it (or email a link to this blog post) to everyone on your QA team.
As an indication that the Hendrikson's Test Heuristics Cheat Sheet works well to uncover defects,
- I wanted to create a set of pairwise tests that could be broadly applicable to test thousands of different applications, I incorporated many ideas from the Test Heuristics Cheat Sheet.
- Ajaxamp 3.3. I intend to use those inputs to test our test design tool, Hexawise.
- The way Hexawise works is that users enter 'things they want to test' into Hexawise on the first of three screens, the 'Define Inputs' screen, then click on 'Create Tests.' Hexawise then uses a scientific approach to maximizing coverage of the combinations of all the 'stuff to be tested' in the fewest possible number of tests. This scientific approach is based on the >40 years of Design of Experiments lessons and includes both pairwise / AllPairs methods as well as more thorough 3-way, 4-way, 5-way and 6-way tests (as well
- Ironically, even before starting to execute the test conditions suggested by Hexawise, I discovered that the special characters that I had input into the 'Define Inputs' screen (which I took from the Test Heuristics Cheat Sheet) triggered a previously unidentified defect in Hexawise itself.
- The fact that it was triggered so quickly in an application that has been live for a year and used thousands of times is a strong indication that using checklists and cheat sheets can be a great way to efficiently find defects.
Why is using checklists to guide your testing often such an efficient and effective way of finding defects? Here's my top ten list:
- The 'bad ideas' have already been weeded out.
- The ideas on the list have found enough defects to make the author of the checklist think there is value in testing the particular idea.
- If you've got a checklist or 'cheat sheet' put together by someone as thoughtful and experienced as the Bachs, Bolton, and Hendrickson, you're getting a highly-condensed executive summary version of many of their valuable insights.
- All testers go through many, many, 'I wonder what would happen if we did this or considered that?' scenarios. The checklists referenced above represent expertise culled from thousands of testing projects.
- Checklists are directly actionable. You can apply them in almost no time at all.
- They work well. See Cem Kaner's slides on the Value of Checklists (11 Mb pdf file).
- They can easily evolve into some of your most powerful test artifacts.
Excel Cheat Sheet 2010
The Cheat Sheet Website
- Start with the lists above. See if each of the ideas for tests trigger defects in your Systems Under Test.
- Find a lot of defects from certain test ideas? Create your own checklist of ideas that worked and iterate them over time. Consider expanding upon the checklist items and concepts that do bear fruit.
- Don't ever find defects from certain of the test ideas? Consider dropping those items from the checklists if they don't bear fruit for you (or put tests for those ideas at the back of your lists and only include tests for them if you have extra time).
- No software or books to buy.
- No courses or conferences to attend.
- As humans, we're naturally forgetful as a species despite our best efforts.
- Checklists are widely used with good results by doctors, lawyers, pilots, software testers, and people going to grocery stores to minimize the effects of these shortcomings.
- Checklists can be used in creating Unit Tests, Assembly Tests, Product Tests, System Tests, Functional Tests, Load Tests, Performance Tests, User Acceptance Tests, etc.
- Checklists can be used by Exploratory Testers and 'script-everything-in-advance' test-case-centric testers.
- Checklists can be used in Agile projects as well as Waterfall projects.
- Using elements from the checklists in a pairwise test will have the added benefit that not only will you test for every one of the testing ideas on the checklist (e.g., XXX) but also, you can easily test for every idea on the checklist **in combination with** every other test idea on the checklist in at least one test case.