Recent Updates RSS Toggle Comment Threads | Keyboard Shortcuts

  • sumit 7:10 pm on April 23, 2012 Permalink | Reply
    Tags: Risk Analysis in Software Testing, Risk Based Testing, Time-Boxing   

    Achieving Time boxing in Testing with Risk Assessment/Analysis 

    Test Execution is one activity which is most difficult to estimate.  Most of the time it happens that if testing team find big chunk of bugs in the software then frequent releases/builds are given to testing team due to which testers face time crunch in test execution. This might results into the skipping of *critical* bugs during testing if high priority areas are not well tested.

    To avoid these situations, Time-boxing should be achieved. In Software Testing, Time-boxing can be achieved by doing Risk Analysis.

    (More …)

     

  • sumit 7:52 pm on February 26, 2012 Permalink | Reply  

    Ignoring the information provided by Test Teams | Management Mistakes 

    True Story of Braidy:

    Braidy once got oppurtunity to work as a tester in a software company. As usual the company lacked testing culture.
    The bugs reported by QA/testing team were not always reviewed and all the bugs were not always fixed. Most of the times, the focus was on fixing the blocker and major issues only. Despite the fact that Braidy and his team was working hard, the information provided by testing was always ignored. Their managers hardly believe what testers uncovered.  They used to say “Let Client report the bug then we will fix this..”. Management team always had predetermined  plans/dates for software delivery. Braidy was not happy with all this. (More …)

     

    • Akash Soni 12:37 am on February 28, 2012 Permalink | Reply

      As a Tester we have to consider the project as the owner and user of that particular requirement.

    • Mitsuko Mundz 5:08 am on March 11, 2012 Permalink | Reply

      “Heya i am for the initial time here. I discovered this board and I to find It really useful & it aided me out much. I’m hoping to present a thing once again and help others like you served me.”

  • sumit 6:05 pm on May 22, 2011 Permalink | Reply  

    Role of a Tester.. 

    Delivery manager/Project Manager to tester: “Is the product ready to deliver?”

    Few thoughts on the above question:

    - Does PM/Delivery manager forget his role in project? Does he forgets tester’s role in the project? why he is asking this to tester?

    - Does this mean he should work on his decision making skills? Why he cannot analyze the data collected by dev/testing teams.

    [Update - 02/27/2012]

    Every manager expects that team members should be pro-active. Team members also expect that managers should be proactive and understand their responsibility. Gerald M. Weinberg also mentions in his book (Perfect Software and other illusions in Software Testing):

    Over-honoring testers: If you let them make your decision for you, then you should step down and let them earn the manager’s salary.

     

     

  • sumit 5:57 pm on May 4, 2011 Permalink | Reply  

    Why one should go for ISTQB Software Testing Certifications? 

    Why one should go for ISTQB –

    - One gets motivated and gain confidence

    - Companies can convince their clients by saying that – We have nn number of certified employees & we can deliver a quality product.

    - It can help you in getting job, because some job descriptions are like – Preferred with ISTQB Certification. You can see lot of examples here.

     

    Apart from above, do you know any reason why one should go for ISTQB/ISEB Software Testing Certifications? Post in comments.

     

    Must Read - ISTQB and AST – Which one should you go for?

     

    • Riyaj 5:20 pm on May 8, 2011 Permalink | Reply

      One gets motivated and gain confidence

      I have met with many ISTQB certified students , who feels that they would get job because they have certification but they need to sruggle a lot , where on paper they are showing the skills but students fails to show the skills in practice.I met with AST certified testers/non certified but skilled ones who have the confidence which comes through below three things:

      1.Testing skills
      2.Better testing skills
      3.more better testing skills.

      “Companies can convince their clients by saying that – We have nn number of certified employees & we can deliver a quality product.”

      Are you people thinking that clients are fooled by numbers? In my view the clients wants the work with better quality and only skilled software testers can do that work.

      “It can help you in getting job, because some job descriptions are like – Preferred with ISTQB Certification. You can see lot of examples here.”

      For sure , this certification will help you to “get in ” but you will not survive until you get the testing skills.

      • sumit 4:20 am on May 15, 2011 Permalink | Reply

        @Riyaj – I have worked for a project where client requirement was atleast nn testers should be iseb/istqb certified.

    • Shyamalaa 10:15 am on March 28, 2012 Permalink | Reply

      By doing those certifications, we can able to learn the concepts and apply those concepts while testing.
      We can differentiate us from the other testers.
      Our certification will also speak about our career achievement.

  • sumit 2:13 pm on May 4, 2011 Permalink | Reply  

    ISTQB and AST – Which one should you go for? 

    The debate on Testing certifications is still going on.. Below are some differences and my experiences on ISTQB Foundations certification and AST’s BBST Foundations course:

     

    ISTQB Foundations AST’s BBST Foundations
    Focus Indirectly forces candidates to mug up/memorize the book Directly forces the students to think, learn, understand and apply.There is no other option left for students. (More …)
     

    • sarita 8:19 pm on May 4, 2011 Permalink | Reply

      i m looking for career in testing done mca, good knowledge of manaul testing but did get job, could you suggest me

  • sumit 6:40 pm on April 26, 2011 Permalink | Reply  

    Some noteworthy points from book The Wisdom of Crowds:

    • Groups do not need to be dominated by exceptionally intelligent people in order to be smart. ~ the wisdom of crowds. Even if most of the people within a group are not especially well-informed or rational,it can still reach a collectively wise decision.
    • Instead of insisting on finding the best possible decision, we will often accept one that seems good enough. And we often let emotion affect our judgment. Yet despite all these limitations, when our imperfect judgments are aggregated in the right way, our collective intelligence is often excellent.
    • One of the striking things about the wisdom of crowds is that even though its effects are all around us, it’s easy to miss, and, even when it’s seen, it can be hard to accept.
    • Chasing the expert is a mistake, and a costly one at that. We should stop hunting and ask the crowd (which, of course, includes the geniuses as well as everyone else) instead. Chances are, it knows.

     

    http://www.amazon.com/Wisdom-Crowds-James-Surowiecki/dp/0385721706

     

  • sumit 6:52 pm on April 25, 2011 Permalink | Reply  

    Recruiting Software Testers – My experiences as an interviewee 

    In the last 4 years, I have undergone some job interviews as interviewee. Some interviews had gone well and I cleared. Some interviews did not go well and I failed to clear. In this post I am going to share my interview experience with two companies as both companies took my interview in a very different manner.

    Sometime back I gave interview in a CMMi level company and in a Non-Cmmi level Company. I passed interviews of both companies but i joined none of these. I like the way the Non-Cmmi level Company took my interview. But I was disappointed with the way – the CMMi level company take my interview. (More …)

     

    • saket sharma 5:18 am on April 26, 2011 Permalink | Reply

      Dear Sir,
      I read your full story about your interview. What i am trying to saying is according to my point of view.
      Yes you are right, Don’t think about the way of your side. Only think about the interviewer. Who is going to take your interview.
      Only clear the interview what is the requirement of the company.
      Everybody having own knowledge & own confidence about in his field. Every company having own interview standard format .
      The Project managers are decided the rounds & interview questions.
      So, they will never think about your level of knowledge & how much u deserve.
      They will always think about you will able to clear all the interview rounds perfectly or,not.
      Just go ahead with your subject knoweldge & clear the interview.

    • itika 5:43 am on April 26, 2011 Permalink | Reply

      lucky guy…

    • Shamayla 6:28 am on April 26, 2011 Permalink | Reply

      Quite Interesting Story! :) And Informative too….
      Thanks For Sharing.

    • divya 6:14 pm on April 27, 2011 Permalink | Reply

      Hey SUMIT !!
      I totally agree with you.I am also looking for job in testing ,But rather than testing your test cases in interviews they go for theoretical question..I dnt know what they want to see in candidate. And problem with me is I dont Have experience in testing so now I dn know how to get started…If you can help me :)

  • sumit 3:43 am on April 21, 2011 Permalink | Reply  

    Favorite Testing Tweets 

    How to figure the value of testing? A start: ask how you value eyeglasses, radios, smoke alarms, yardsticks: things that help you observe. Here – https://twitter.com/#!/michaelbolton/status/17909459689

    A microscope produces nothing of value on its own, but it helps people to observe things that provide or threaten value. Here – https://twitter.com/#!/michaelbolton/status/17909541879

    You don’t evaluate your eyeglasses by how many vision cases they executed today. Here – https://twitter.com/#!/michaelbolton/status/17910243521

    How many fire prevention cases did your smoke alarm execute today. Here – https://twitter.com/#!/michaelbolton/status/17910281645

    Wnen people say that semantics aren’t important, I don’t understand what they mean, but I guess it doesn’t matter. Here – https://twitter.com/#!/michaelbolton/status/17912608272

    instead of asking if the sw meets the spec, ask if the spec writer understands the business. Here – https://twitter.com/#!/mheusser/status/20301744012

    Today I heard a derivative from the “No user would ever do that!” statement: “The code works according to current use”. Here – https://twitter.com/#!/MichelKraaij/status/53048570135330816

    Perspective: when under pressure to release the product, remember that the world has survived until now without it. Here – https://twitter.com/#!/michaelbolton/status/60676529159553025

    Bringing about change within your team is satisfying, Influencing and persuading senior stakeholders….priceless! Here - https://twitter.com/#!/charrett/status/132294460737458176

    Metrics are not meant to be interpreted they are required to be self evident. Here - https://twitter.com/#!/sbarber/status/132108348563791872

    If humans were perfect thinkers, we wouldn’t need to test our work. Here - https://twitter.com/#!/skalra/status/72585120992858112

    When I hear “It’s better for you, Customer, to report that than me,” I detect an organization that listens to neither customers nor workers. Here - https://twitter.com/#!/michaelbolton/status/123257010362916865

     

     

  • sumit 5:54 am on February 24, 2010 Permalink | Reply  

    Testing ISN’T (is) About Learning. It is About Thinking. 

    Changed title, as it is misleading – Refer comments section.

    A good tester is a good thinker. A long time I give my following thoughts on testing here

    There are many testing institutes in India. They all can give us technical and bookish knowledge on software testing.

    But this is not enough. The main asset of a tester is ‘the way the tester thinks’. And this is not given by those institutes.. (More …)

     

    • Michael Bolton 7:48 pm on April 18, 2010 Permalink | Reply

      I agree that testing is about thinking, but the notion that testing isn’t about learning strikes me as silly. Testing is learning about the product in service of our clients and the rest of the project community. What is the point of thinking if it’s not in service of learning?

      —Michael B.

    • sumitkalra 9:11 am on April 21, 2010 Permalink | Reply

      Hello Michael, thanks for your comments.

      I agree Testing is learning about the product in service of our clients. Here is just trying to this apart from testing you need to think how actually things work.

      There can be some cases where (while doing testing) testers just implement/execute only “testing techniques – boundary value, equivalence part,etc” & check alignments, links etc and don’t think on other areas.

      These above Checks actually sometimes are not required in early stages of testing a product. Instead of validating the above, keep focus on the product functionality and think how actually it should work.

      Hope you understand my point.

    • Vignesh 12:17 pm on April 24, 2010 Permalink | Reply

      The view which you have told is very useful… But as a beginner we still need more detailed information.. Please do give more links in your site related to software testing. n short we need a better guide to show us the right path in our career..

      Thanks

      Vignesh

  • sumit 6:42 am on February 23, 2010 Permalink | Reply  

    How to Fake a Test Project – by James Bach in STPConference 2009 

    Few months back, I got the highlights of STPConference 2009 email. One of the highlight is “How to Fake a Test Project”.

    ————————————————————

    Behave conventionally. Squander energy. Deflect scrutiny. Say you tested it, but spend most of your time playing Spider Solitaire instead. Be sure to submit a few bugs though, because you don’t want to make it too obvious that you’re not really testing. (More …)

     

← Older posts

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel