Manual Testing

Manual Testing: It is a process in which all the phase of software testing life cycle like test planning, test development, test execution result analysis, bug tracking and reporting are accomplished successfully normally with human efforts.


Testing: An examination of the behavior of a program by executing on sample data sets.
OR
A Testing is a process of executing a program with the intent of finding bugs, and to improve the quality.

Software Testing: The process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies specific requirement or to indentify difference b/w expected and actual result.

Purpose of Testing:
1. To uncover hidden errors
2. To achieve the maximum usability of the system
3. To Demonstrate expected performance of the system.

General reasons for Defect found in software system are:
 It improperly interprets requirements
 The users specify the wrong requirement
 The requirement are un-correctly recorded
 Error in program coding
 The design specification are incorrect
 Data entry errors

Types of Testing:

1. White Box Testing:
     o Testing is based on the source code.
     o Testing a functional with knowing the internal structure of the program.

Structure of the program:
     o Types: Statement coverage, Decision Coverage, Condition Coverage.

White box Testing can drive test case to ensure:
1. All independent paths are exercised at least once.
2. All logical decisions are executed for both true and false paths
3. All loops are executed at their boundaries and within operational bounds.
4. All internal data structure is executed to ensure validity.

Why white box testing when black box testing is used?
  • To confirm logical errors and incorrect assumptions are most likely to be made when coding for special cases. Need to ensure there execution path are tested.
  • May find assumption about execution path incorrect, and so make design errors. White box testing can find these errors.
  • Typographical errors are random. Just as likely to be on an obscure logical path as on a mainstream path.
Test Engineer Responsibilities:
• Analysis on Requirement document (SRS).
• Developing test cases.
• Test data planning and capturing
• Test execution
• Developing automated scripts for regression testing
• Preparing test documentation.
• Defect tracking and reporting.
• Participating in reviews.

To Test Effectively Test Engineer Must:
• Thoroughly understand the system.
• Thoroughly understand the technology the system is begin developed on.
• Possess creativity, insight and business knowledge
• Have the breaking attitude.
• Have good error guessing skills.

Verification: Ensure the system complies with organization standards and process using non-executable methods.
Ex: Requirement review, design review, code walkthrough, code inspection.

Validation: Ensure the system satisfies specified requirements by executing series of tests.
Ex: unit testing, Integration Testing, System Testing UAT….

Difference b/w White box and Black box Testing:



Advantage:

• Most effective on larger units of code than glass box testing.
• Tester needs no knowledge of implementation including specific programming languages.
• Tester and programmers are independent of each other
• Tests are done from user’s point of view.
• Test cases can be designed as soon as the specifications are complete.

Disadvantage:
• Only a small number of possible inputs can actually be tested to test every possible input stream would take nearly forever.
• Without clear and concise specification test cases are hard to design.
• There may be necessary repetition of test of inputs if the testers are not informed of test cases the programmer has already tried.
• May leave many program path untested.
• Cannot be directed toward specific segments of code which may be very complex and therefore error prone.
• Most testing related research has been directed toward glass box testing.


Automation Testing:  It is process in which all the drawbacks of manual testing are addressed (overcome) properly and provides speed and accuracy to the existing testing phase.

Comments

  1. Hello,
    The Article on Manual Testing along with detail information is nice give detail information about it.Thanks for Sharing the detail information article on Manual testing. Software Testing Company

    ReplyDelete
  2. The great service in this blog and the nice technology is visible in this blog. I am really very happy for the nice approach is visible in this blog and thank you very much for using the nice technology in this blog

    selenium training in chennai|
    selenium training in bangalore|

    ReplyDelete
  3. Informative post.Thanks to share complete details regarding testing.
    best mobile service center in chennai

    ReplyDelete
  4. Thank you all... I will keep update the blogs with more information. Thanks once again.

    ReplyDelete
  5. Thanks for this blog post admin, you have done really nice work.
    Manual testing

    ReplyDelete
  6. This comment has been removed by the author.

    ReplyDelete
  7. FESHOP ACC RU LEGIT FSH 2017 RU FESHOP.RU FESHOP18 FESHOP A very awesome blog post. We are really grateful for your blog post. You will find a lot of approaches after visiting your post.

    ReplyDelete
  8. I would like to thank you for the efforts you have made in writing this article about Software Testing Services in Boston. I am hoping the same best work from you in the future as well Software Testing Companies in Chicago. Thank you for sharing such a great blog post Software Testing Companies in Dallas with us this blog is really informative and useful, keep it up..

    Read more - Software Testing Services in Florida

    ReplyDelete

Post a Comment

Popular posts from this blog

Software Development Life Cycle

STLC and Testing Terminology