Page 4 of 5 FirstFirst ... 2345 LastLast
Results 61 to 80 of 91

Thread: Guidelines for Manual Testing

  1. #61
    Expert Member
    Join Date
    Apr 2008
    Answers
    1,859

    Re: Guidelines for Manual Testing

    hi friend,

    Welcome to the forum. Please don't mess anything with old thread. If you want to introduce yourself please use the below section

    Geeks Community -Sub-Forums: Get Together

    Thanks,
    Deepa

    Arise Awake And Stop Not Till The Goal Is Reached

  2. #62
    Junior Member
    Join Date
    Jan 2010
    Answers
    1

    Re: Guidelines for Manual Testing

    thats good


  3. #63
    Junior Member
    Join Date
    Feb 2010
    Answers
    1

    Re: Guidelines for Manual Testing

    This is awesome stuff


  4. #64
    Junior Member
    Join Date
    Feb 2010
    Answers
    2

    Re: Guidelines for Manual Testing

    thxx..dudee...


  5. #65
    Expert Member
    Join Date
    Apr 2008
    Answers
    1,859

    Re: Guidelines for Manual Testing

    Quote Originally Posted by seeku View Post
    thxx..dudee...
    hi friend,

    If you need to thank the user you can just click on thanks button.

    Thanks,
    Deepa

    Arise Awake And Stop Not Till The Goal Is Reached

  6. #66
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Guidelines for Manual Testing

    Quote Originally Posted by kappies View Post
    Hi

    This is a very interesting article. I was wondering though if there is an industry standard to define the timescales of testing? Example, 20 % of the development days??

    Do you know where I can find a definitive answer on this?
    It depends on timelines.

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  7. #67
    Junior Member
    Join Date
    Jun 2010
    Answers
    1

    Re: Guidelines for Manual Testing

    Hi all,

    I am a trainee tester,,,,,,can anybody send me wts the exact difference b/w walkthroughs,reviews & inspections,,,,,if possible with examples,,,,,
    pls kindly revert to this post if u know ans,,,,,,

    Thanks & Regards,
    venu


  8. #68
    Junior Member
    Join Date
    Jun 2010
    Answers
    1

    Re: Guidelines for Manual Testing

    The review means a meeting conducted by a group of members to find out the defects in the earlier stage itself.
    The difference b/w walkthrough and inspection are
    Walkthrough is the semi formal reviewe, there may or may not requires the paper works
    Inspection is the formal review conducted by other than testing team specifically by Project manager with TL and tester of testing group. It requires a valid doc. preparation.


  9. #69
    Junior Member
    Join Date
    Jul 2010
    Answers
    1

    Re: Guidelines for Manual Testing

    Thanks for very useful information ganesh


  10. #70
    Junior Member
    Join Date
    Jul 2010
    Answers
    1

    Smile Re: Guidelines for Manual Testing

    hi can anyone help me to know abt manual testing and about loadrunner!


  11. #71
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Guidelines for Manual Testing

    Quote Originally Posted by carojude View Post
    hi can anyone help me to know abt manual testing and about loadrunner!
    It's better if you read any book on testing explaining what is testing, and face any issue, then discuss here.

    One good book, is software testing by Ron Patton.

    Thanks.

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  12. #72
    Junior Member
    Join Date
    Jul 2009
    Answers
    1

    Re: Guidelines for Manual Testing

    Hi..............


  13. #73
    Contributing Member
    Join Date
    Apr 2008
    Answers
    66

    Re: Guidelines for Manual Testing

    Very very helpful documents.Can you upload some document related to SDLC and V-model


  14. #74
    Contributing Member
    Join Date
    Sep 2010
    Answers
    32

    Re: Guidelines for Manual Testing

    Helpul Doc

    Last edited by emmily; 09-16-2010 at 05:01 AM.

  15. #75
    Contributing Member
    Join Date
    Sep 2010
    Answers
    32

    Re: Guidelines for Manual Testing

    Test Plan is a High Level Document that contains What to Test ,How to Test ,Who to Test etc .Test Plan will varies with company .sme company has a standard format for the test Plan
    The following contents are in Test Plan
    1.intoduction
    2.Revision history
    3.Software Requiremnts /Harware Requirements
    4.Features to be tested
    5.Features not to be tested
    6.Risk Areas
    7.Test deliverables
    8.Testing tasks
    9.Environmental needs
    10.Responsibilities
    11.Staffing and training needs
    12.Schedule
    13.Priority and Severity Defn
    14.Approvals


  16. #76
    Contributing Member
    Join Date
    Sep 2010
    Answers
    32

    Re: Guidelines for Manual Testing

    Quote Originally Posted by sarvesh4u View Post
    very very helpful documents.can you upload some document related to sdlc and v-model
    the systems development life cycle (sdlc), or software development life cycle in systems engineering, information systems and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. The concept generally refers to computer or information systems. there are 5 phases in sdlc requirements gathering and analysisthe goal of system analysis is to determine where the problem is in an attempt to fix the system. This step involves breaking down the system in different pieces to analyze the situation, analyzing project goals, breaking down what needs to be created and attempting to engage users so that definite requirements can be defined. Requirements analysis sometimes requires individuals/teams from client as well as service provider sides to get detailed and accurate requirements....often there has to be a lot of communication to and from to understand these requirements. Requirement gathering is the most crucial aspect as many times communication gaps arise in this phase and this leads to validation errors and bugs in the software program. designin systems, design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems. The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input design. build or codingmodular and subsystem programming code will be accomplished during this stage. Unit testing and module testing are done in this stage by the developers. This stage is intermingled with the next in that individual modules will need testing before integration to the main project. testingthe code is tested at various levels in software testing. Unit, system and user acceptance testings are often performed. This is a grey area as many different opinions exist as to what the stages of testing are and how much if any iteration occurs. Iteration is not generally part of the waterfall model, but usually some occur at this stage. Below are the following types of testing: data set testing. Unit testing system testing integration testing black box testing white box testing regression testing automation testing user acceptance testing performance testing production process that ensures that the program performs the intended task. operations and maintenance the deployment of the system includes changes and enhancements before the decommissioning or sunset of the system. Maintaining the system is an important aspect of sdlc. As key personnel change positions in the organization, new changes will be implemented, which will require system updates. The v-model is a software development process (also applicable to hardware development) which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical v shape the main phases of v model is verification phase and validation phase 1 verification phases 1.1 requirements analysis 1.2 system design 1.3 architecture design 1.4 module design 2 validation phases 2.1 unit testing 2.2 integration testing 2.3 system testing 2.4 user acceptance testing for more infor go to Systems Development Life Cycle - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/v-model...e_development)


  17. #77
    Junior Member
    Join Date
    Oct 2010
    Answers
    1

    Re: Guidelines for Manual Testing

    Hi..
    Its really a very good and useful post for us I like your given information.I am very excited about this post.


  18. #78
    Shridatta Kulkarni
    Guest

    Re: Guidelines for Manual Testing

    hi.... i m new to software testing field .... can i know how is my feature.... in this field.... and what is the differnce between ... smoke testing and sanity testing and dry run ...


  19. #79
    Junior Member
    Join Date
    Dec 2010
    Answers
    3

    Re: Guidelines for Manual Testing

    @ Compatability Testing - Compatibility Testing is a performed to verify whether a software is compatible with all other supported software and hardware


  20. #80
    Junior Member
    Join Date
    Dec 2010
    Answers
    3

    Re: Guidelines for Manual Testing

    Smoke Testing is a quick test performed on the major functionalities of software

    Sanity Testing is a process of checking the basic functionality of software before proceeding to the in dept testing


  21.  Sponsored Ads
    Ad


     
Page 4 of 5 FirstFirst ... 2345 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact