User Tag List

Results 1 to 4 of 4
  1. #1
    Junior Member
    Join Date
    Jan 2005
    Post Thanks / Like
    0 Post(s)
    0 Thread(s)

    Questions on testing???????/

    Hi all,

    Can any one tell me:
    1. In what stage of developement does testing starts?
    2. In testing who creats the test plans is it the tester or team lead or qa mananger?

    3. What is the role of unix in testing and mostly on what operating systems testers perform testing?

    Please answer to these questions in detail....

    Thank you in advance


  2. #2
    Senior Member
    Join Date
    May 2001
    Toronto, Ontario, Canada
    Post Thanks / Like
    0 Post(s)
    0 Thread(s)

    Re: Questions on testing???????/

    1. With some approaches, testing (the kind designed to demonstrate desired functionality; "confirmatory" testing) starts before development. Test-Driven Development presupposes that you write a test that is designed to fail, and then you write code to pass it. At each modification of the code, whether adding features or rewriting certain bits to improve on them (also known as refactoring), you run all previous tests to make sure they pass; then you create a new, failing test; and then you make your change. These tests are all automated, so they go fast, and they allow programmers to make changes with confidence and security; as long as there are failing tests, you keep refining things until they all pass again.

    With other approaches, testing of the same kind (that is, confirmatory and typically automated tests) can start immediately after some code is written, or might never get done at all.

    Another kind of testing, testing that is designed to pose and answer questions related to quality about the existing product (or "investigative" testing) can also be started at any time after some code exists. Some schools of thought have it that developers should produce a body of code and then, at some point that someone deems proper, hand it over to testers in a big package. Some schools believe in lots of scripted test cases and don't test until those are available; others take a more lightweight approach. Other schools of thought choose smaller packages in exchange for more rapid feedback. There are thousands of opinions and no provably correct way to do it. I favour documentation that is as lightweight as can fit and fill the mission of testing; others here prefer approaches that place more value on documentation.

    Test plans can created by anyone who has been assigned to the job; no one answer there either. Unless someone else is completely responsible for the quality of his work, each individual does some planning--if only for himself--to some degree.

    I don't know how answer the question about the role of Unix in testing. Testers use the operating system(s) required by the applications under test, by the testing tools that the testers use, and by the other, non-testing-specific tools that the testers use. Since the majority of systems in the world are Windows systems, one would presume that the majority of testing is done on Windows systems (insert your own joke here).

    Kaner has written two foundational books on testing; I'd recommend those for starters. Other choices for reading will depend upon the style of testing favoured by your organization.

    ---Michael B.

  3. #3
    Moderator JakeBrake's Avatar
    Join Date
    Dec 2000
    St. Louis - Year 2025
    Post Thanks / Like
    0 Post(s)
    0 Thread(s)

    Re: Questions on testing???????/

    I think the best place to get answers to those questions is in a book - since it normally takes a book to answer those questions and all the context that go with each question. Please look this over:


    AND Explore/Search the Functional Testing and Quality Methodologies forums.

  4. #4
    Junior Member
    Join Date
    Feb 2005
    Santa Clara
    Post Thanks / Like
    0 Post(s)
    0 Thread(s)

    Re: Questions on testing???????/

    1. Testing can be done on any stage of the process, but it starts to become more costly as development progresses.
    The sooner the bug is found and fixed, the cheaper.
    2. It depends on the company structure. Anyone from QA team should be able to do this.
    Just in case if would like to know more about Test Plan:
    A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the ”why” and “how” of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project:
    • Title
    • Identification of software including version/release numbers
    • Revision history of document including authors, dates, approvals
    • Table of Contents
    • Purpose of document, intended audience
    • Objective of testing effort
    • Software product overview
    • Relevant related document list, such as requirements, design documents, other test plans, etc.
    • Relevant standards or legal requirements
    • Traceability requirements
    • Relevant naming conventions and identifier conventions
    • Overall software project organization and personnel/contact-info/responsibilities
    • Test organization and personnel/contact-info/responsibilities
    • Assumptions and dependencies
    • Project risk analysis
    • Testing priorities and focus
    • Scope and limitations of testing
    • Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable
    • Outline of data input equivalence classes, boundary value analysis, error classes
    • Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems
    • Test environment validity analysis - differences between the test and production systems and their impact on test validity.
    • Test environment setup and configuration issues
    • Software migration processes
    • Software CM processes
    • Test data setup requirements
    • Database setup requirements
    • Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs
    • Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs
    • Test automation - justification and overview
    • Test tools to be used, including versions, patches, etc.
    • Test script/test code maintenance processes and version control
    • Problem tracking and resolution - tools and processes
    • Project test metrics to be used
    • Reporting requirements and testing deliverables
    • Software entrance and exit criteria
    • Initial sanity testing period and criteria
    • Test suspension and restart criteria
    • Personnel allocation
    • Personnel pre-training needs
    • Test site/location
    • Outside test organizations to be utilized and their purpose, responsibilities, deliverables, contact persons, and coordination issues
    • Relevant proprietary, classified, security, and licensing issues.
    • Open issues
    • Appendix - glossary, acronyms, etc.

    3. UNIX doesn't have any role in testing but testing in UNIX does.
    Use scripting when you test application on UNIX platform.

    Best regards,



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 03:40 PM.

Copyright BetaSoft Inc.