Beruflich Dokumente
Kultur Dokumente
Ans. Operation of a system or application under controlled conditions and evaluating the
results. The controlled conditions must include both normal and abnormal conditions. It is
oriented to detection.
3. In March of 2002 it was reported that software bugs in Britain's national tax system
resulted in more than 100,000 erroneous tax overcharges.
Q8. What are the common problems in the software development process?
Ans.
Poor requirements
Unrealistic schedule
Inadequate testing
A request to pile on new features after development is unnderway.
Miscommunication
Solid requirements
Realistic schedules
Adequate testing
stick to initial requirements where feasible
require walkthroughs and inspections when appropriate
2. If the risk is lower, management and organizational buy-in and QA implementation may
be a slower.
- Application name
- The function, module, name
- Bug ID
- Bug reporting date
- Status
- Test case ID
- Bug description
- Steps needed to reproduce the bug
- Names and/or descriptions of file/data/messages/etc. used in test
- Snapshot that would be helpful in finding the cause of the problem
- Severity estimate
- Was the bug reproducible?
- Name of tester
- Description of problem cause (filled by developers)
- Description of fix (filled by developers)
- Code section/file/module/class/method that was fixed (filled by developers)
- Date of fix (filled by developers)
- Date of retest or regression testing
- Any remarks or comments
Q21. What is verification?
Ans. It involves reviews and meetings to evaluate documents, plans, code, requirements, and
specifications. It can be done with checklists, issues lists, walkthroughs, and inspection
meetings etc.
Q28. What if the project isn't big enough to justify extensive testing?
Ans. Do risk analysis. See the impact of project errors, not the size of the project.
- What are the expected loads on the server and what kind of performance is expected on the
client side?
- Who is the target audience?
- Will down time for server and content maintenance / upgrades be allowed?
- What kinds of security will be required and what is it expected to do?
- How reliable are the site's Internet / intranet connections required to be?
- How do the internet / intranet affect backup system or redundant connection requirements
and testing?
- What variations will be allowed for targeted browsers?
- Will there be any standards or requirements for page appearance and / or graphics
throughout a site or parts of a site?
- How will internal and external links be validated and updated?
- How are browser caching and variations in browser option settings?
- How are flash, applets, java scripts, ActiveX components, etc. to be maintained, tracked,
controlled, and tested?
- From the usability point of view consider the following: