All About Testing

Goals for the Facebook Connect integration are:
- New User Sign Up without needing to create a site-specific password (email address needed)
- Ability for existing users to link with their Facebook account
- 1:1 mapping between accounts on your site and Facebook accounts
- Single sign-on experience

Few Test cases will be in such a way:
Sign Up should fail if the user denies permission to the app (category: sign up)

Since we need access to an email address, Sign Up should fail if the user provides publish permission but denies email permission (category: sign up)

If the user provides an email address that already exists in your system, fail Sign Up.

Attempting to Sign Up with a Facebook account that's already linked and authorized should result in the Sign In experience (category: sign up, sign in)

Attempting to Sign In with a Facebook account that the app hasn't seen before should lead to the Sign Up experience, i.e. create a new account (category: sign up, sign in)

Like the page to see more of these Test cases and Tips and Tricks....

Tip of the day....

Three types of quality attributes:
1. Product Operations
2. Product Revision
3. Product Transition

Quality factors are mapping its attributes:
Product Operations:
• Correctness: does it do what I want?
• Reliability: does it do accurately all the time?
• Efficiency: will it run on my machine as well as it can?
• Integrity: is it secure?
• Usability: can I run it?
Product Revision:
• Maintainability: can I fix it?
• Flexibility: can I change it?
• Testability: can I test it?
Product Transition:
• Portability: will I be able to use on another machine?
• Reusability: will I be able to reuse some of the software?
• Interoperability: will I be able to interface it with another machine?

Hello All,

This page is all about testing or testers. Request you all to please write a short introduction of yours so that we all can know each other.... This introduction can include your skills, what you are working on etc...