Some Funny Types of Testing

Types of Testing – from

  • Aggression Testing: If this doesn’t work, I’m gonna kill somebody.
  • Compression Testing: []
  • Confession Testing: Okay, Okay, I did program that bug.
  • Congressional Testing:Are you now, or have you ever been a bug?
  • Depression Testing:If this doesn’t work, I’m gonna kill myself.
  • Egression Testing: Uh-oh, a bug… I’m outta here.
  • Digression Testing: Well, it works, but can I tell you about my truck…
  • Expression Testing: #@%^&*!!!, a bug.
  • Obsession Testing: I’ll find this bug if it’s the last thing I do.
  • Oppression Testing: Test this now!
  • Poission Testing: Alors! Regardez le poission!
  • Repression Testing: It’s not a bug, it’s a feature.
  • Secession Testing: The bug is dead! Long lives the bug!
  • Suggestion Testing: Well, it works but wouldn’t it be better if…



Android 4.0 – great new features

I’ll sure want this version of Android and I hope I’ll get the Galaxy Nexus also with it 😀

  1. Android Beam
  2. Data usage tools
  3. Voice typing
  4. Face unlock
  5. Universal copy-and-paste
  6. Quick responses to calls
  7. Screenshots
  8. Camera improvements

You can read here the details for each feature.

Mobile testing: strategy tests

Mobile applications may be downloaded for the first time and used only once or twice. Unless the value of an application is compelling, users may not be coming back to use it. They will ignore the app or even delete it after some time. Here are nine types of tests that should be included in your mobile test strategy to ensure your mobile apps are highly effective and will keep your users coming back for more.

1. Conceptual testing

Mobile apps and the features planned for them need to be socialized before development starts with at least an informal focus group consisting of typical users in the demographics to which they are targeted. Mobile apps are used in ways different from how users approach a client application or a Web-based application. Interactions need to be quick, short and appropriate for smaller form factor screens. Users also expect seamless integration with social networks and online resources. Sounding typical users out before any development is done can eliminate unnecessary features and ensure the right ones are in, before too much development effort is expended.

2. Unit testing, system testing

If the mobile app has a variety of components or logs into a back-end server, downloads or uploads data between the app and a server, regular unit testing and system testing may all need to be in place and executed extensively. If the app does not work well with the server, the overall experiences are bound to suffer.

3. Mobile user experience testing

Once a mobile app is ready with all features, it may be worthwhile to do a round of mobile user experience testing. This is giving the users the app on their mobile device before any formal release. They use the application in its entirety and report on what the experience was like, overall. This will enable developers to remove impediments to a smooth, continuous and pleasant overall user experience. When a user completes a task or an entire use case, then you can validate whether features you have implemented all fit together nicely. If not, adjustments can be made.
Continue reading

Acceptance Test Engineering Guide

Why acceptance testing?

Patterns & practices has produced just a few guides related to testing (including performance testing, security testing of web apps, and testing of .NET application blocks). However, we hear a lot of requests from our customers for guidance on testing and test strategy in general, and also guidance on every type of testing you can think of. Based on this customer feedback, and a look at what guidance was available, we determined that acceptance testing was the next area to invest in.

What is acceptance testing?

Working definitions for a number of terms are available in our Draft Glossary. The current definition that is framing our work and discussions is:

  • Acceptance Testing: Planned evaluation of a system by customers/customer proxies to assess to what degree it satisfies their expectations.

We are open to suggestions on this and other terms. Please leave comments on the Draft Glossary page.

What are we producing?

This guide is the first in the series of three dedicated to acceptance testing and requirements engineering:

  • Acceptance test engineering guide
  • Acceptance test automation guide
  • Tool support for acceptance test-driven development.

The first guide will cover the discipline of acceptance testing from several perspectives and contexts. It will provide models, heuristics and a set of actionable job aides rooted in a sample app. The focus is on:

  • How to Plan for Acceptance Testing
  • What Kinds of Acceptance Tests to Run
  • How to Create and Run Acceptance Tests
  • Defining What “Done” Means
  • How to Justify Your Approach

What types of things you can learn in the guide?

If any of the following goals apply to you, you will want to check out the the guide.

You can download the Acceptance Test Engineering Guide from here.

MSDN: Unit Testing Web Applications


Unit testing, sometimes referred to as developer testing, focuses on testing small pieces of code, such as a class, that a developer is writing. These tests are critical for helping you ensure that the pieces you build work as expected and will operate correctly when combined with other parts of the application. Such testing helps support management of the application over time by ensuring that changes you make don’t inadvertently affect other parts of the system.

This chapter shows you how to get started unit testing JavaScript as well as server-side code, but does not cover all aspects of unit testing. References to more detailed discussions about unit testing can be found at the end of this chapter. While the unit tests for the Mileage Stats application were written using Test-First Development (or Test-Driven Development), this chapter will only cover the test-oriented aspects of unit testing, not the design aspects.

This chapter does not cover other important aspects of testing, such as performance, stress, security, automation, deployment, localization, and globalization. Nor does it discuss other important aspects to consider when testing the client side, such as cross-browser compatibility or usability. However, these areas are important for you to consider when testing your web application.

In this chapter you will learn:

  • How to get started unit testing your JavaScript and ASP.NET MVC code.
  • The arrange-act-assert unit test structure.
  • Techniques to isolate your tests and components.
  • Things you should consider when testing your jQuery UI widgets.

The technologies discussed in this chapter are QUnit, used to test your JavaScript and jQuery client-side code, and and Moq, for testing your server-side, ASP.NET MVC code.
Continue reading

Job hunter’s guide to using social media effectively

From New Grad Life blog

Your Social Media Presence

Social media also makes it a whole lot easier for HR to research who you are and get a little background. Maybe more than professional background, so it’s very important that you get out there and see what your social media profiles and presence looks like through a recruiters eyes. As a job seeker this is definitely key! Do some searches on yourself. Try Google first because it’s the most common. Dig more than a few pages down and see what comes up. Then give Yahoo and MSN a try too. You very well may find different information.

Make a list of the positive and negative references out there that impact you as a job applicant and make a plan to deal with them. Ask your college room-mate to take down the picture of you dancing on the bar in a toga with a beer bong. Some things may not be correctable. Have your explanation ready so you’re not caught off-guard. Odds are you won’t need it but be prepared.

Balance out negative things said about you on sites like MySpace and FaceBook by asking your friends to post referrals or positive comments. “Just checked out Anna’s portfolio and she positively ROCKS!!!” can’t hurt you, especially if it’s true. If you have enough positive comments and information about you, the one bad reference will dissapear under the avalanche of positive information.

Your profiles

If you’re new to social media this is a good time to get involved as an online job seeker. There are a host of options out there to help you put your best foot forward and land a job. Creating Twitter, Facebook and Linkedin profiles allows you to reach a variety of people. Create the profiles carefully and choose the people you connect to with an eye for professionalism. I can’t get into friending strategy here, but remember you want to focus on quality not quantity and make sure to build your relationships so people are in a position to recommend you for a job.


There are a wonderful array of tools to create a resume on-line. You should think about who you’re going to be talking to and create a resume that suits the need. Maybe you’ll have a different resume for each field you’re qualified in.

VisualCV – Lets a job seeker create a resume and upload portfolio items, PPT slide sets, Audio or Video to enhance the presentation. Layout is modifiable and the user can download as a PDF to print or email.

Razume helps a job seeker build your resume and then you can get crowd-source reviews from other users in the community. Fine tuning with this kind of input from your peers can really make a difference. The site also offers job search right on the site.

ResumeSocial is a social resume community similar to Razume, but it’s got the added benefit of user reviews of your cover letters, follow ups job search and a career center with useful tips and info.


Some networks will be more useful than others depending on what your needs are. You may want to look at some forums or blogs where people in your industry hang out. If your business is corporate, you may want to connect on the professional networks like Xing and Linkedin.
Continue reading