• Testing concepts
  • Friday, 26 July 2013

    WhiteBoxTesting V/s BlackBoxTesting

    Everyone might be confused there might be many types of Testing which are involved and why they are called as Boxes.
    Well mainly Box determines the Visibility or Non Visibility of what an Box can contain
    Here White BoxTesting is where we can see whats there inside the Box and its visible
    Some of the Different types are
    API testing (application programming interface)
    Static testing
    Code coverage 
    Here entire concepts are basically are coding pint of view where normally the person should be having coding knowledge so that he can view each and every point what is happening in the code and he can test by himself.

    BlackBox Testing:
    This is common and most familiar type of Testing which determines the Box is invisible and we cannot see what the Box contains i.e code cannot be viewed .
    Here BlackBox testing where normally testers use have different types of concepts used in it
    depending on what the exact specification is there for functionality.
    Few Techniques are:
    Equivalence partitioning.
    Boundary value analysis
    State Transition

    There are many other types of Testing like grey box testing, glass box testing but these are just the terms used mainly for confusion but hardly it is used except the above two.


    Monday, 22 July 2013

    Reasons for Test Cases

    Test Cases are mainly step by step procedure for checking the functionality of the application.
    If a each module functionality has to be checked Test cases has to be written from looking into requirements
    From this at the initial stage itself the issues or specially known as Bugs can be found out and it would be easier for the developer to fix the issues rather than at the end point where everything has to meet the deadline of the Project.
    And the Tester also gets to know the Flow of the application where all possible inputs can be tested using Functionality testing
    Test Case structure:
    Test CaseId:
    Expected Result:
    Actual Result:
    Difference between Positive Test case and Negative Test Case
    Many of them get confused on what are Positive Test case and Negative Test case

    Well to make it simpler the,
    Positive Test case are Valid Test Cases u enter
    Negative Test case are In Valid Test Cases u enter.
    Most of the Testing has to be done using Negative Test case as the main objective of Testing
    is to Find Bugs and that is by entering Negative scenarios that will try to break the application
    and make it stable.
    Testing is mainly concept of Destructive approach than Constructive approach

    Sunday, 21 July 2013

    Dedicated Testing on Web Based Application

    Hello Everybody,
    Today I have got the work of testing the application as dedicated tester where i have to go
    through all functionalities of application. So going through the requirements of it.
    How come today posting many Bugs but what will happen to the developer
    i guess he may not like it i guess :).
    But Testing is Testing not a fight between Developer its all about the Clients not about Developer. 

    Friday, 19 July 2013

    Developers swap their position to Testers

    1. Its always a point to discuss who is going to become a good tester
    2. A tester which is testing knowledge or an Developer who has Developing code knowledge.
    3. Today what if Developer swaps his designation to Tester what would happen anybody thought?
    4. The application might not be as stable as the Tester does his own way of testing.
    5. Reasons are many but few of it is like
        a. Developers always focus on their coding knowledge and test based on that
        b. Going by Developers knowledge he might become good tester by ways of Constructor only not
            as  Destructor whereas Tester are known for Destructing than Constructing
        c. Developers are might be good in testing others work but not on their work :)
    6. Hence Few scenarios  of Developer

    Fight between Developer and Tester

    Today I had fight between a developer regarding one issue where he had completely rejected the bug
    But thanks to the video recorder i had sent to him that was the proof where the bug was recorded
    Developer had fixed the bug and sent  a mail the it was never a bug.
    Then I showed the video and called an meeting with Manager to show the Proof what the Develoepr has done .
    Finally this time Tester won the battle. :)

    Thursday, 18 July 2013


    1. Developers always believe they are correct and Testers Prove them wrong.
    2. Developers always say the Bugs Posted are Invalid and but Testers make them Valid
    3. Conversation between Developer and Tester should be in Professional manner
    4. Professional important because   If they are friends they might compromise on the application
    5.  Professional important because If they are enemies the application might go hay wire.