Showing posts with label Idea. Show all posts
Showing posts with label Idea. Show all posts

Wednesday, January 15, 2014

I See You

Product instructions in the form of user documentation (or) handbook are a valuable element to any product. It is vital to assess if this content is usable and has a positive impact on a user’s experience.

When instructional aides are too difficult to understand, the result can be worse than a product. By putting yourself in a user’s shoes and statistics, you’ll be able to assess if the instructional content meets the needs of the anticipated audience.

Try to have a document for each functional portion [Functional Break-up Document{FBD}], so that it might help you one day...



Monday, February 4, 2013

Remote Testers


There is an aged-old saying like Testers should be divided from Dev/BA team & they should work independently.
The above statement is linked to the bizarre style of testing, as what is the role of testers and what testers should perform.
If you are cautious on the thought that your testing team must be isolated from other teams, then there is a better possibility that you and your team will achieve more testing; (since you are free from expressing your own test ideas without other’s suggestion/feeds).


Friday, December 30, 2011

Let the clock talk

Software Testing is the art of ideas. Thinking in the clock’s approach is forever superior. Clock is the only thing which always thinks about ‘Time’, as its profession is that. As a tester, we involve in most of the time linked procedure. They are;


  • Time to investigate a new feature.
  • Time to analyze a requirement.
  • Time to acknowledge a design page.
  • Time to write a test plan.
  • Time to carve-in a test case.
  • Time to carry-out a test case.
  • Time to re-test a test case.
  • Time to write down a test report.
  • Time to release the product.
  • Time to take rest.


Monday, December 26, 2011

CAR in IT!!!

Question: What is CAR?
Answer: Chuck Away the Requirements.

- Understanding of the proposed requirements.
- Pointing out the gaps and raising queries.
- Quick assessment & certification of a feature.
- Determining if an idea is achievable or not.
- Test coverage for that feature.