Testin Faqs

8/2/2019 Testin Faqs

1/34

Software QA/Testing

Glossary and Technical FAQs

Q1. What is verification?

A: Verification ensures the product is designed to deliver all functionality to the customer; it typicallyinvolves reviews and meetings to evaluate documents, plans, code, requirements andspecifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings.You CAN learn to do verification, with little or no outside help. Get CAN get free information. Click

on a link!

Q2. What is validation?

A: Validation ensures that functionality, as defined in requirements, is the intended behavior of theproduct; validation typically involves actual testing and takes place after verifications are completed.

Q3. What is a walkthrough?

A:A walkthrough is an informal meeting for evaluation or informational purposes. A walkthrough isalso a process at an abstract level. It's the process of inspecting software code by following pathsthrough the code (as determined by input conditions and choices made along the way). Thepurpose of code walkthroughs is to ensure the code fits the purpose. Walkthroughs also offeropportunities to assess an individual's or team's competency.

Q4. What is an inspection?

A:An inspection is a formal meeting, more formalized than a walkthrough and typicallyconsists of 3-10 people including a moderator, reader (the author of whatever is beingreviewed) and a recorder (to make notes in the document). The subject of the inspection istypically a document, such as a requirements document or a test plan. The purpose of an

inspection is to find problems and see what is missing, not to fix anything. The result of themeeting should be documented in a written report. Attendees should prepare for this typeof meeting by reading through the document, before the meeting starts; most problems arefound during this preparation. Preparation for inspections is difficult, but is one of the mostcost-effective methods of ensuring quality, since bug prevention is more cost effective thanbug detection.


2/34

Q5. What is quality?

A: Quality software is software that is reasonably bug-free, delivered on time and withinbudget, meets requirements and expectations and is maintainable. However, quality is asubjective term. Quality depends on who the customer is and their overall influence in thescheme of things. Customers of a software development project include end-users,customer acceptance test engineers, testers, customer contract officers, customer

management, the development organization's management, test engineers, testers,salespeople, software engineers, stockholders and accountants. Each type of customer willhave his or her own slant on quality. The accounting department might define quality interms of profits, while an end-user might define quality as user friendly and bug free.

Q6. What is good code?

A:A good code is code that works, is free of bugs and is readable and maintainable.Organizations usually have coding standards all developers should adhere to, but everyprogrammer and software engineer has different ideas about what is best and what are toomany or too few rules. We need to keep in mind that excessive use of rules can stifle bothproductivity and creativity. Peer reviews and code analysis tools can be used to check for

problems and enforce standards.

Q7. What is good design?

A: Design could mean to many things, but often refers to functional design or internaldesign. Good functional design is indicated by software functionality can be traced back tocustomer and end-user requirements. Good internal design is indicated by software codewhose overall structure is clear, understandable, easily modifiable and maintainable; isrobust with sufficient error handling and status logging capability; and works correctly whenimplemented.

Q8. What is software life cycle?

A: Software life cycle begins when a software product is first conceived and ends when it isno longer in use. It includes phases like initial concept, requirements analysis, functionaldesign, internal design, documentation planning, test planning, coding, documentpreparation, integration, testing, maintenance, updates, re-testing and phase-out.

Q9. Why are there so many software bugs?

A: Generally speaking, there are bugs in software because of unclear requirements,software complexity, programming errors, changes in requirements, errors made in bugtracking, time pressure, poorly documented code and/or bugs in tools used in softwaredevelopment.

There are unclear software requirements because there is miscommunication as towhat the software should or shouldn't do.

Software complexity. All of the followings contribute to the exponential growth insoftware and system complexity: Windows interfaces, client-server and distributedapplications, data communications, enormous relational databases and the sheer size ofapplications.

Programming errors occur because programmers and software engineers, likeeveryone else, can make mistakes.


3/34

As to changing requirements, in some fast-changing business environments,continuously modified requirements are a fact of life. Sometimes customers do notunderstand the effects of changes, or understand them but request them anyway. And thechanges require redesign of the software, rescheduling of resources and some of the workalready completed have to be redone or discarded and hardware requirements can beeffected, too.

Bug tracking can result in errors because the complexity of keeping track of

changes can result in errors, too. Time pressures can cause problems, because scheduling of software projects isnot easy and it often requires a lot of guesswork and when deadlines loom and the crunchcomes, mistakes will be made.

Code documentation is tough to maintain and it is also tough to modify code that ispoorly documented. The result is bugs. Sometimes there is no incentive for programmersand software engineers to document their code and write clearly documented,understandable code. Sometimes developers get kudos for quickly turning out code, orprogrammers and software engineers feel they cannot have job security if everyone canunderstand the code they write, or they believe if the code was hard to write, it should behard to read.

Software development tools , including visual tools, class libraries, compilers,scripting tools, can introduce their own bugs. Other times the tools are poorly documented,

which can create additional bugs.

Q10. How do you introduce a new software QA process?

A: It depends on the size of the organization and the risks involved. For large organizationswith high-risk projects, a serious management buy-in is required and a formalized QAprocess is necessary. For medium size organizations with lower risk projects, managementand organizational buy-in and a slower, step-by-step process is required. Generallyspeaking, QA processes should be balanced with productivity, in order to keep anybureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process ismore appropriate. A lot depends on team leads and managers, feedback to developers andgood communication is essential among customers, managers, developers, test engineersand testers. Regardless the size of the company, the greatest value for effort is in

managing requirement processes, where the goal is requirements that are clear, completeand testable.

Q11. Give me five common problems that occur duringsoftware development.

A: Poorly written requirements, unrealistic schedules, inadequate testing, adding newfeatures after development is underway and poor communication.

1. Requirements are poorly written when requirements are unclear, incomplete, too general,or not testable; therefore there will be problems.

2. The schedule is unrealistic if too much work is crammed in too little time.3. Software testing is inadequate if none knows whether or not the software is any good until

customers complain or the system crashes.4. It's extremely common that new features are added after development is underway.5. Miscommunication either means the developers don't know what is needed, or customers

have unrealistic expectations and therefore problems are guaranteed.


4/34

Q12. Do automated testing tools make testing easier?

A: Yes and no. For larger projects, or ongoing long-term projects, they can be valuable. But forsmall projects, the time needed to learn and implement them is usually not worthwhile. A commontype of automated tool is the record/playback type. For example, a test engineer clicks through allcombinations of menu choices, dialog box choices, buttons, etc. in a GUI and has an automatedtesting tool record and log the results. The recording is typically in the form of text, based on a

scripting language that the testing tool can interpret. If a change is made (e.g. new buttons areadded, or some underlying code in the application is changed), the application is then re-tested by

just playing back the recorded actions and compared to the logged results in order to check effectsof the change. One problem with such tools is that if there are continual changes to the productbeing tested, the recordings have to be changed so often that it becomes a very time-consumingtask to continuously update the scripts. Another problem with such tools is the interpretation of theresults (screens, data, logs, etc.) that can be a time-consuming task. You CAN learn to useautomated testing tools, with little or no outside help. Get CAN get free information. Click on a link!

Q13. Give me five solutions to problems that occur duringsoftware development.

A: Solid requirements, realistic schedules, adequate testing, firm requirements and goodcommunication.

1. Ensure the requirements are solid, clear, complete, detailed, cohesive, attainable andtestable. All players should agree to requirements. Use prototypes to help nail downrequirements.

2. Have schedules that are realistic. Allow adequate time for planning, design, testing, bugfixing, re-testing, changes and documentation. Personnel should be able to complete theproject without burning out.

3. Do testing that is adequate. Start testing early on, re-test after fixes or changes, and planfor sufficient time for both testing and bug fixing.

4. Avoid new features. Stick to initial requirements as much as possible. Be prepared todefend design against changes and additions, once development has begun and be

prepared to explain consequences. If changes are necessary, ensure they're adequatelyreflected in related schedule changes. Use prototypes early on so customers' expectationsare clarified and customers can see what to expect; this will minimize changes later on.

5. Communicate. Require walkthroughs and inspections when appropriate; make extensiveuse of e-mail, networked bug-tracking tools, tools of change management. Ensuredocumentation is available and up-to-date. Use documentation that is electronic, not paper.Promote teamwork and cooperation.

Q14. What makes a good test engineer?

A: Rob Davis is a good test engineer because he

Has a "test to break" attitude,

Takes the point of view of the customer,

Has a strong desire for quality,

Has an attention to detail, He's also

Tactful and diplomatic and

Has good a communication skill, both oral and written. And he

Has previous software development experience, too.


5/34

Good test engineers have a "test to break" attitude. We, good test engineers, take the point of viewof the customer, have a strong desire for quality and an attention to detail. Tact and diplomacy areuseful in maintaining a cooperative relationship with developers and an ability to communicate withboth technical and non-technical people. Previous software development experience is also helpfulas it provides a deeper understanding of the software development process, gives the test engineeran appreciation for the developers' point of view and reduces the learning curve in automated testtool programming.

Q15. What makes a good QA engineer?

A: The same qualities a good test engineer has are useful for a QA engineer. Additionally, RobDavis understands the entire software development process and how it fits into the businessapproach and the goals of the organization. Rob Davis'communication skills and the ability tounderstand various sides of issues are important. Good QA engineers understand the entiresoftware development process and how it fits into the business approach and the goals of theorganization. Communication skills and the ability to understand various sides of issues areimportant.

Q16. What makes a good resume?

A: On the subject of resumes, there seems to be an unending discussion of whether you should orshouldn't have a one-page resume. The followings are some of the comments I have personallyheard: "Well, Joe Blow (car salesman) said I should have a one-page resume." "Well, I read a bookand it said you should have a one page resume." "I can't really go into what I really did because if Idid, it'd take more than one page on my resume." "Gosh, I wish I could put my job at IBM on myresume but if I did it'd make my resume more than one page, and I was told to never make theresume more than one page long." "I'm confused, should my resume be more than one page? I feellike it should, but I don't want to break the rules." Or, here's another comment, "People just don'tread resumes that are longer than one page." I have heard some more, but we can start with these.So what's the answer? There is no scientific answer about whether a one-page resume is right orwrong. It all depends on who you are and how much experience you have. The first thing to look athere is the purpose of a resume. The purpose of a resume is to get you an interview. If the resume

is getting you interviews, then it is considered to be a good resume. If the resume isn't getting youinterviews, then you should change it. The biggest mistake you can make on your resume is tomake it hard to read. Why? Because, for one, scanners don't like odd resumes. Small fonts canmake your resume harder to read. Some candidates use a 7-point font so they can get the resumeonto one page. Big mistake. Two, resume readers do not like eye strain either. If the resume ismechanically challenging, they just throw it aside for one that is easier on the eyes. Three, thereare lots of resumes out there these days, and that is also part of the problem. Four, in light of thecurrent scanning scenario, more than one page is not a deterrent because many will scan yourresume into their database. Once the resume is in there and searchable, you have accomplishedone of the goals of resume distribution. Five, resume readers don't like to guess and most won't callyou to clarify what is on your resume. Generally speaking, your resume should tell your story. Ifyou're a college graduate looking for your first job, a one-page resume is just fine. If you have alonger story, the resume needs to be longer. Please put your experience on the resume so resumereaders can tell when and for whom you did what. Short resumes -- for people long on experience-- are not appropriate. The real audience for these short resumes is people with short attentionspans and low IQ. I assure you that when your resume gets into the right hands, it will be readthoroughly

Q17. What makes a good QA/Test Manager?

A: QA/Test Managers are familiar with the software development process; able to maintainenthusiasm of their team and promote a positive atmosphere; able to promote teamwork to


6/34

increase productivity; able to promote cooperation between Software and Test/QA Engineers, havethe people skills needed to promote improvements in QA processes, have the ability to withstandpressures and say *no* to other managers when quality is insufficient or QA processes are notbeing adhered to; able to communicate with technical and non-technical people; as well as able torun meetings and keep them focused.

Q18. What is the role of documentation in QA?

A: Documentation plays a critical role in QA. QA practices should be documented, so that they arerepeatable. Specifications, designs, business rules, inspection reports, configurations, codechanges, test plans, test cases, bug reports, user manuals should all be documented. Ideally, thereshould be a system for easily finding and obtaining of documents and determining what documentwill have a particular piece of information. Use documentation change management, if possible.

Q19. What about requirements?

A: Requirement specifications are important and one of the most reliable methods of insuringproblems in a complex software project is to have poorly documented requirement specifications.Requirements are the details describing an application's externally perceived functionality and

properties. Requirements should be clear, complete, reasonably detailed, cohesive, attainable andtestable. A non-testable requirement would be, for example, "user-friendly", which is too subjective.

A testable requirement would be something such as, "the product shall allow the user to enter theirpreviously-assigned password to access the application". Care should be taken to involve all of aproject's significant customers in the requirements process. Customers could be in-house orexternal and could include end-users, customer acceptance test engineers, testers, customercontract officers, customer management, future software maintenance engineers, salespeople andanyone who could later derail the project. If his/her expectations aren't met, they should be includedas a customer, if possible. In some organizations, requirements may end up in high-level projectplans, functional specification documents, design documents, or other documents at various levelsof detail. No matter what they are called, some type of documentation with detailed requirementswill be needed by test engineers in order to properly plan and execute tests. Without suchdocumentation there will be no clear-cut way to determine if a software application is performing

correctly. You CAN learn to capture requirements, with little or no outside help. Get CAN get freeinformation. Click on a link!

Q20. What is a test plan?

A:A software project test plan is a document that describes the objectives, scope, approach andfocus of a software testing effort. The process of preparing a test plan is a useful way to thinkthrough the efforts needed to validate the acceptability of a software product. The completeddocument 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 none outside the test group willbe able to read it.

Q21. What is a test case?A:A test case is a document that describes an input, action, or event and its expected result, inorder to determine if a feature of an application is working correctly. A test case should containparticulars such as a...

Test case identifier;

Test case name;

Objective;


7/34

Test conditions/setup;

Input data requirements/steps, and

Expected results.

Please note, the process of developing test cases can help find problems in the requirements ordesign of an application, since it requires you to completely think through the operation of theapplication. For this reason, it is useful to prepare test cases early in the development cycle, if

possible.

Q22. What should be done after a bug is found?

A: When a bug is found, it needs to be communicated and assigned to developers that can fix it.After the problem is resolved, fixes should be re-tested. Additionally, determinations should bemade regarding requirements, software, hardware, safety impact, etc., for regression testing tocheck the fixes didn't create other problems elsewhere. If a problem-tracking system is in place, itshould encapsulate these determinations. A variety of commercial, problem-tracking/managementsoftware tools are available. These tools, with the detailed input of software test engineers, will givethe team complete information so developers can understand the bug, get an idea of its severity,reproduce it and fix it.

Q23. What is configuration management?

A: Configuration management (CM) covers the tools and processes used to control,coordinate and track code, requirements, documentation, problems, change requests,designs, tools, compilers, libraries, patches, changes made to them and who makes thechanges. Rob Davis has had experience with a full range of CM tools and concepts. RobDavis can easily adapt to your software tool and process needs.

Q24. What if the software is so buggy it can't be tested at all?

A: In this situation the best bet is to have test engineers go through the process ofreporting whatever bugs or problems initially show up, with the focus being on critical bugs.Since this type of problem can severely affect schedules and indicates deeper problems inthe software development process, such as insufficient unit testing, insufficient integrationtesting, poor design, improper build or release procedures, managers should be notifiedand provided with some documentation as evidence of the problem.

Q25. How do you know when to stop testing?

A: This can be difficult to determine. Many modern software applications are so complexand run in such an interdependent environment, that complete testing can never be done.Common factors in deciding when to stop are...

Deadlines, e.g. release deadlines, testing deadlines;

Test cases completed with certain percentage passed;

Test budget has been depleted;

Coverage of code, functionality, or requirements reaches a specified point;

Bug rate falls below a certain level; or

Beta or alpha testing period ends.


8/34

Q26. What if there isn't enough time for thorough testing?

A: Since it's rarely possible to test every possible aspect of an application, every possiblecombination of events, every dependency, or everything that could go wrong, risk analysisis appropriate to most software development projects. Use risk analysis to determine wheretesting should be focused. This requires judgment skills, common sense and experience.The checklist should include answers to the following questions:

Which functionality is most important to the project's intended purpose?

Which functionality is most visible to the user?

Which functionality has the largest safety impact?

Which functionality has the largest financial impact on users?

Which aspects of the application are most important to the customer?

Which aspects of the application can be tested early in the development cycle?

Which parts of the code are most complex and thus most subject to errors?

Which parts of the application were developed in rush or panic mode?

Which aspects of similar/related previous projects caused problems?

Which aspects of similar/related previous projects had large maintenanceexpenses?

Which parts of the requirements and design are unclear or poorly thought out? What do the developers think are the highest-risk aspects of the application?

What kinds of problems would cause the worst publicity?

What kinds of problems would cause the most customer service complaints?

What kinds of tests could easily cover multiple functionalities?

Which tests will have the best high-risk-coverage to time-required ratio?

Q27. What if the project isn't big enough to justifyextensive testing?

A: Consider the impact of project errors, not the size of the project. However, if extensivetesting is still not justified, risk analysis is again needed and the considerations listed under

"What if there isn't enough time for thorough testing?" do apply. The test engineer thenshould do "ad hoc" testing, or write up a limited test plan based on the risk analysis.

Q28. What can be done if requirements are changingcontinuously?

A: Work with management early on to understand how requirements might change, so thatalternate test plans and strategies can be worked out in advance. It is helpful if theapplication's initial design allows for some adaptability, so that later changes do not requireredoing the application from scratch. Additionally, try to...

Ensure the code is well commented and well documented; this makes changeseasier for the developers.

Use rapid prototyping whenever possible; this will help customers feel sure of theirrequirements and minimize changes.

In the project's initial schedule, allow for some extra time to commensurate withprobable changes.

Move new requirements to a 'Phase 2' version of an application and use theoriginal requirements for the 'Phase 1' version.

Negotiate to allow only easily implemented new requirements into the project;move more difficult, new requirements into future versions of the application.


9/34

Ensure customers and management understand scheduling impacts, inherent risksand costs of significant requirements changes. Then let management or the customersdecide if the changes are warranted; after all, that's their job.

Balance the effort put into setting up automated testing with the expected effortrequired to redo them to deal with changes.

Design some flexibility into automated test scripts;

Focus initial automated testing on application aspects that are most likely to

remain unchanged; Devote appropriate effort to risk analysis of changes, in order to minimizeregression-testing needs;

Design some flexibility into test cases; this is not easily done; the best bet is tominimize the detail in the test cases, or set up only higher-level generic-type test plans;

Focus less on detailed test plans and test cases and more on ad-hoc testing withan understanding of the added risk this entails.

Q29. What if the application has functionality that wasn't inthe requirements?

A: It may take serious effort to determine if an application has significant unexpected or

hidden functionality, which it would indicate deeper problems in the software developmentprocess. If the functionality isn't necessary to the purpose of the application, it should beremoved, as it may have unknown impacts or dependencies that were not taken intoaccount by the designer or the customer.If not removed, design information will be needed to determine added testing needs orregression testing needs. Management should be made aware of any significant addedrisks as a result of the unexpected functionality. If the functionality only affects areas, suchas minor improvements in the user interface, it may not be a significant risk.

Q30. How can software QA processes be implementedwithout stifling productivity?

A: Implement QA processes slowly over time. Use consensus to reach agreement onprocesses and adjust and experiment as an organization grows and matures. Productivitywill be improved instead of stifled. Problem prevention will lessen the need for problemdetection. Panics and burnout will decrease and there will be improved focus and lesswasted effort. At the same time, attempts should be made to keep processes simple andefficient, minimize paperwork, promote computer-based processes and automated trackingand reporting, minimize time required in meetings and promote training as part of the QAprocess. However, no one, especially talented technical types, like bureaucracy and in theshort run things may slow down a bit. A typical scenario would be that more days ofplanning and development will be needed, but less time will be required for late-night bugfixing and calming of irate customers.

Q31. What if organization is growing so fast that fixed QA

processes are impossible?A: This is a common problem in the software industry, especially in new technology areas. There isno easy solution in this situation, other than...

Hire good people (i.e. hire Rob Davis)

Ruthlessly prioritize quality issues and maintain focus on the customer;

Everyone in the organization should be clear on what quality means to the customer.


10/34

Q32. How is testing affected by object-oriented designs?

A:A well-engineered object-oriented design can make it easier to trace from code to internaldesign to functional design to requirements. While there will be little affect on black box testing(where an understanding of the internal design of the application is unnecessary), white-box testingcan be oriented to the application's objects. If the application was well designed this can simplifytest design.

Q33. Why do you recommended that we test during the designphase?

A: Because testing during the design phase can prevent defects later on. We recommend verifyingthree things... Verify the design is good, efficient, compact, testable and maintainable.

1. Verify the design meets the requirements and is complete(specifies all relationships between modules, how to pass data, whathappens in exceptional circumstances, starting state of each module andhow to guarantee the state of each module).2. Verify the design incorporates enough memory, I/O devices and

quick enough runtime for the final product.

Q34. What is software quality assurance?

A: Software Quality Assurance, when Rob Davis does it, is oriented to *prevention*. Itinvolves the entire software development process. Prevention is monitoring and improvingthe process, making sure any agreed-upon standards and procedures are followed andensuring problems are found and dealt with. Software Testing, when performed by RobDavis, is also oriented to *detection*. Testing involves the operation of a system orapplication under controlled conditions and evaluating the results. Organizations varyconsiderably in how they assign responsibility for QA and testing. Sometimes they're thecombined responsibility of one group or individual. Also common are project teams, whichinclude a mix of test engineers, testers and developers who work closely together, with

overall QA processes monitored by project managers. It depends on what best fits yourorganization's size and business structure. Rob Davis can provide QA and/or Software QA.This document details some aspects of how he can provide software testing/QA service.For more information, e-mail [email protected]

Q35. What is quality assurance?

A: Quality Assurance ensures all parties concerned with the project adhere to the processand procedures, standards and templates and test readiness reviews.Rob Davis' QA service depends on the customers and projects. A lot will depend on teamleads or managers, feedback to developers and communications among customers,managers, developers' test engineers and testers.

Q36. Process and procedures - why follow them?

A: Detailed and well-written processes and procedures ensure the correct steps are beingexecuted to facilitate a successful completion of a task. They also ensure a process isrepeatable. Once Rob Davis has learned and reviewed customer's business processes andprocedures, he will follow them. He will also recommend improvements and/or additions.
mailto:[email protected]:[email protected]


11/34

Q37. Standards and templates - what is supposed to be in adocument?

A:All documents should be written to a certain standard and template. Standards and

templates maintain document uniformity. It also helps in learning where information islocated, making it easier for a user to find what they want. Lastly, with standards andtemplates, information will not be accidentally omitted from a document. Once Rob Davishas learned and reviewed your standards and templates, he will use them. He will alsorecommend improvements and/or additions.

Q38. What are the different levels of testing?

A: Rob Davis has expertise in testing at all testing levels listed below. At each test level, hedocuments the results. Each level of testing is either considered black or white box testing.

Q39. What is black box testing?A: Black box testing is functional testing, not based on any knowledge of internal software

design or code. Black box testing are based on requirements and functionality. Q40.What is white box testing?

A: White box testing is based on knowledge of the internal logic of an application's code.Tests are based on coverage of code statements, branches, paths and conditions.

Q41. What is unit testing?

A: Unit testing is the first level of dynamic testing and is first the responsibility ofdevelopers and then that of the test engineers. Unit testing is performed after the expected

test results are met or differences are explainable/acceptable.

Q42. What is parallel/audit testing?

A: Parallel/audit testing is testing where the user reconciles the output of the new systemto the output of the current system to verify the new system performs the operationscorrectly.

Q43. What is functional testing?

A: Functional testing is black-box type of testing geared to functional requirements of anapplication. Test engineers *should* perform functional testing.

Q44. What is usability testing?

A: Usability testing is testing for 'user-friendliness'. Clearly this is subjective and dependson the targeted end-user or customer. User interviews, surveys, video recording of usersessions and other techniques can be used. Programmers and developers are usually notappropriate as usability testers.


12/34

Q45. What is incremental integration testing?

A: Incremental integration testing is continuous testing of an application as newfunctionality is recommended. This may require that various aspects of an application'sfunctionality are independent enough to work separately, before all parts of the programare completed, or that test drivers are developed as needed. This type of testing may beperformed by programmers, software engineers, or test engineers.

Q46. What is integration testing?

A: Upon completion of unit testing, integration testing begins. Integration testing is blackbox testing. The purpose of integration testing is to ensure distinct components of theapplication still work in accordance to customer requirements. Test cases are developedwith the express purpose of exercising the interfaces between the components. Thisactivity is carried out by the test team.

Integration testing is considered complete, when actual results and expected results areeither in line or differences are explainable/acceptable based on client input.

Q47. What is system testing?

A: System testing is black box testing, performed by the Test Team, and at the start of thesystem testing the complete system is configured in a controlled environment. The purposeof system testing is to validate an application's accuracy and completeness in performingthe functions as designed. System testing simulates real life scenarios that occur in a"simulated real life" test environment and test all functions of the system that are requiredin real life. System testing is deemed complete when actual results and expected resultsare either in line or differences are explainable or acceptable, based on client input.Upon completion of integration testing, system testing is started. Before system testing, allunit and integration test results are reviewed by Software QA to ensure all problems havebeen resolved. For a higher level of testing it is important to understand unresolvedproblems that originate at unit and integration test levels. You CAN learn system testing,with little or no outside help. Get CAN get free information. Click on a link!

Q48. What is end-to-end testing?

A: Similar to system testing, the *macro* end of the test scale is testing a completeapplication in a situation that mimics real world use, such as interacting with a database,using network communication, or interacting with other hardware, application, or system.

Q49. What is regression testing?

A: The objective of regression testing is to ensure the software remains intact. A baseline

set of data and scripts is maintained and executed to verify changes introduced during therelease have not "undone" any previous code. Expected results from the baseline arecompared to results of the software under test. All discrepancies are highlighted andaccounted for, before testing proceeds to the next level.

Q50. What is sanity testing?

A: Sanity testing is performed whenever cursory testing is sufficient to prove theapplication is functioning according to specifications. This level of testing is a subset of


13/34

regression testing. It normally includes a set of core tests of basic GUI functionality todemonstrate connectivity to the database, application servers, printers, etc.

Q51. What is performance testing?

A:Although performance testing is described as a part of system testing, it can beregarded as a distinct level of testing. Performance testing verifies loads, volumes andresponse times, as defined by requirements.

Q52. What is load testing?

A: Load testing is testing an application under heavy loads, such as the testing of a website under a range of loads to determine at what point the system response time willdegrade or fail.

Q53. What is installation testing?

A: Installation testing is testing full, partial, upgrade, or install/uninstall processes. The

installation test for a release is conducted with the objective of demonstrating productionreadiness. This test includes the inventory of configuration items, performed by theapplication's System Administration, the evaluation of data readiness, and dynamic testsfocused on basic system functionality. When necessary, a sanity test is performed,following installation testing.

Q54. What is security/penetration testing?

A: Security/penetration testing is testing how well the system is protected againstunauthorized internal or external access, or willful damage. This type of testing usuallyrequires sophisticated testing techniques.

Q55. What is recovery/error testing?A: Recovery/error testing is testing how well a system recovers from crashes, hardwarefailures, or other catastrophic problems.

Q56. What is compatibility testing?

A: Compatibility testing is testing how well software performs in a particular hardware,software, operating system, or network environment.

Q57. What is comparison testing?

A: Comparison testing is testing that compares software weaknesses and strengths tothose of competitors' products.

Q58. What is acceptance testing?

A:Acceptance testing is black box testing that gives the client/customer/project managerthe opportunity to verify the system functionality and usability prior to the system beingreleased to production. The acceptance test is the responsibility of the client/customer orproject manager, however, it is conducted with the full support of the project team. The test


14/34

team also works with the client/customer/project manager to develop the acceptancecriteria.

Q59. What is alpha testing?

A:Alpha testing is testing of an application when development is nearing completion. Minordesign changes can still be made as a result of alpha testing. Alpha testing is typicallyperformed by end-users or others, not programmers, software engineers, or test engineers.

Q60. What is beta testing?

A: Beta testing is testing an application when development and testing are essentiallycompleted and final bugs and problems need to be found before the final release. Betatesting is typically performed by end-users or others, not programmers, software engineers,or test engineers.

Q61. What testing roles are standard on most testingprojects?

A: Depending on the organization, the following roles are more or less standard on mosttesting projects: Testers, Test Engineers, Test/QA Team Lead, Test/QA Manager, System

Administrator, Database Administrator, Technical Analyst, Test Build Manager and TestConfiguration Manager. Depending on the project, one person may wear more than onehat. For instance, Test Engineers may also wear the hat of Technical Analyst, Test BuildManager and Test Configuration Manager. You CAN get a job in testing. Click on a link!

Q62. What is a Test/QA Team Lead?

A: The Test/QA Team Lead coordinates the testing activity, communicates testing status tomanagement and manages the test team.

Q63. What is a Test Engineer?

A: Test Engineers are engineers who specialize in testing. We, test engineers, create testcases, procedures, scripts and generate data. We execute test procedures and scripts,analyze standards of measurements, evaluate results of system/integration/regressiontesting. We also...

Speed up the work of the development staff;

Reduce your organization's risk of legal liability;

Give you the evidence that your software is correct and operates properly;

Improve problem tracking and reporting;

Maximize the value of your software; Maximize the value of the devices that use it;

Assure the successful launch of your product by discovering bugs and designflaws, before users get discouraged, before shareholders loose their cool and beforeemployees get bogged down;

Help the work of your development staff, so the development team can devote itstime to build up your product;

Promote continual improvement;


15/34

Provide documentation required by FDA, FAA, other regulatory agencies and yourcustomers;

Save money by discovering defects 'early' in the design process, before failuresoccur in production, or in the field;

Save the reputation of your company by discovering bugs and design flaws; beforebugs and design flaws damage the reputation of your company.

Q64. What is a Test Build Manager?

A: Test Build Managers deliver current software versions to the test environment, installthe application's software and apply software patches, to both the application and theoperating system, set-up, maintain and back up test environment hardware. Depending onthe project, one person may wear more than one hat. For instance, a Test Engineer mayalso wear the hat of a Test Build Manager.

Q65. What is a System Administrator?

A: Test Build Managers, System Administrators, Database Administrators deliver currentsoftware versions to the test environment, install the application's software and apply

software patches, to both the application and the operating system, set-up, maintain andback up test environment hardware. Depending on the project, one person may wear morethan one hat. For instance, a Test Engineer may also wear the hat of a System

Administrator.

Q66. What is a Database Administrator?

A: Test Build Managers, System Administrators and Database Administrators delivercurrent software versions to the test environment, install the application's software andapply software patches, to both the application and the operating system, set-up, maintainand back up test environment hardware. Depending on the project, one person may wearmore than one hat. For instance, a Test Engineer may also wear the hat of a Database

Administrator.

Q67. What is a Technical Analyst?

A: Technical Analysts perform test assessments and validate system/functional testrequirements. Depending on the project, one person may wear more than one hat. Forinstance, Test Engineers may also wear the hat of a Technical Analyst.

Q68. What is a Test Configuration Manager?

A: Test Configuration Managers maintain test environments, scripts, software and testdata. Depending on the project, one person may wear more than one hat. For instance,

Test Engineers may also wear the hat of a Test Configuration Manager.

Q69. What is a test schedule?

A: The test schedule is a schedule that identifies all tasks required for a successful testingeffort, a schedule of all test activities and resource requirements.

Q70. What is software testing methodology?


16/34

A: One software testing methodology is the use a three step process of...

1. Creating a test strategy;2. Creating a test plan/design; and3. Executing tests.

This methodology can be used and molded to your organization's needs. RobDavis believes that using this methodology is important in the development and inongoing maintenance of his customers' applications.

Q71. What is the general testing process?

A: The general testing process is the creation of a test strategy (which sometimes includesthe creation of test cases), creation of a test plan/design (which usually includes test casesand test procedures) and the execution of tests.

Q72. How do you create a test strategy?

A: The test strategy is a formal description of how a software product will be tested. A teststrategy is developed for all levels of testing, as required. The test team analyzes therequirements, writes the test strategy and reviews the plan with the project team. The testplan may include test cases, conditions, the test environment, a list of related tasks,pass/fail criteria and risk assessment.

Inputs for this process:

A description of the required hardware and software components, including testtools. This information comes from the test environment, including test tool data.

A description of roles and responsibilities of the resources required for the test andschedule constraints. This information comes from man-hours and schedules.

Testing methodology. This is based on known standards. Functional and technical requirements of the application. This information comesfrom requirements, change request, technical and functional design documents.

Requirements that the system can not provide, e.g. system limitations.

Outputs for this process:

An approved and signed off test strategy document, test plan, including test cases.

Testing issues requiring resolution. Usually this requires additional negotiation atthe project management level.

Q73. How do you create a test plan/design?

A: Test scenarios and/or cases are prepared by reviewing functional requirements of the releaseand preparing logical groups of functions that can be further broken into test procedures. Testprocedures define test conditions, data to be used for testing and expected results, includingdatabase updates, file outputs, report results. Generally speaking...

Test cases and scenarios are designed to represent both typical and unusual situationsthat may occur in the application.


17/34

Test engineers define unit test requirements and unit test cases. Test engineers alsoexecute unit test cases.

It is the test team who, with assistance of developers and clients, develops test cases andscenarios for integration and system testing.

Test scenarios are executed through the use of test procedures or scripts.

Test procedures or scripts define a series of steps necessary to perform one or more testscenarios.

Test procedures or scripts include the specific data that will be used for testing the processor transaction.

Test procedures or scripts may cover multiple test scenarios.

Test scripts are mapped back to the requirements and traceability matrices are used toensure each test is within scope.

Test data is captured and base lined, prior to testing. This data serves as the foundation forunit and system testing and used to exercise system functionality in a controlledenvironment.

Some output data is also base-lined for future comparison. Base-lined data is used tosupport future application maintenance via regression testing.

A pretest meeting is held to assess the readiness of the application and the environmentand data to be tested. A test readiness document is created to indicate the status of theentrance criteria of the release.


Approved Test Strategy Document.

Test tools, or automated test tools, if applicable.

Previously developed scripts, if applicable.

Test documentation problems uncovered as a result of testing. A good understanding of software complexity and module path coverage, derivedfrom general and detailed design documents, e.g. software design document, source codeand software complexity data.


Approved documents of test scenarios, test cases, test conditions and test data.

Reports of software design issues, given to software developers for correction.

Q74. How do you execute tests?

A: Execution of tests is completed by following the test documents in a methodical manner.As each test procedure is performed, an entry is recorded in a test execution log to notethe execution of the procedure and whether or not the test procedure uncovered anydefects. Checkpoint meetings are held throughout the execution phase. Checkpointmeetings are held daily, if required, to address and discuss testing issues, status andactivities.


18/34

The output from the execution of test procedures is known as test results. Testresults are evaluated by test engineers to determine whether the expected results havebeen obtained. All discrepancies/anomalies are logged and discussed with the softwareteam lead, hardware test lead, programmers, software engineers and documented forfurther investigation and resolution. Every company has a different process for logging andreporting bugs/defects uncovered during testing.

A pass/fail criteria is used to determine the severity of a problem, and results are

recorded in a test summary report. The severity of a problem, found during system testing,is defined in accordance to the customer's risk assessment and recorded in their selectedtracking tool.

Proposed fixes are delivered to the testing environment, based on the severity ofthe problem. Fixes are regression tested and flawless fixes are migrated to a new baseline.Following completion of the test, members of the test team prepare a summary report. Thesummary report is reviewed by the Project Manager, Software QA Manager and/or TestTeam Lead.

After a particular level of testing has been certified, it is the responsibility of theConfiguration Manager to coordinate the migration of the release software components tothe next test level, as documented in the Configuration Management Plan. The software isonly migrated to the production environment after the Project Manager's formalacceptance.

The test team reviews test document problems identified during testing, and

update documents where appropriate.


Approved test documents, e.g. Test Plan, Test Cases, Test Procedures.

Test tools, including automated test tools, if applicable.

Developed scripts.

Changes to the design, i.e. Change Request Documents.

Test data.

Availability of the test team and project team.

General and Detailed Design Documents, i.e. Requirements Document, SoftwareDesign Document.

A software that has been migrated to the test environment, i.e. unit tested code,via the Configuration/Build Manager.

Test Readiness Document.

Document Updates.


Log and summary of the test results. Usually this is part of the Test Report. Thisneeds to be approved and signed-off with revised testing deliverables.

Changes to the code, also known as test fixes.

Test document problems uncovered as a result of testing. Examples areRequirements document and Design Document problems.

Reports on software design issues, given to software developers for correction.Examples are bug reports on code issues.

Formal record of test incidents, usually part of problem tracking.

Base-lined package, also known as tested source and object code, ready formigration to the next level


19/34

Q75. What testing approaches can you tell me about?

A: Each of the followings represents a different testing approach:

Black box testing,

White box testing,

Unit testing, Incremental testing,

Integration testing,

Functional testing,

System testing,

End-to-end testing,

Sanity testing,

Regression testing,

Acceptance testing,

Load testing,

Performance testing,

Usability testing,

Install/uninstall testing,

Recovery testing,

Security testing,

Compatibility testing,

Exploratory testing, ad-hoc testing,

User acceptance testing,

Comparison testing,

Alpha testing,

Beta testing, and

Mutation testing.

Q76. What is stress testing?

A: Stress testing is testing that investigates the behavior of software (and hardware) underextraordinary operating conditions. For example, when a web server is stress tested, testing aimsto find out how many users can be on-line, at the same time, without crashing the server. Stresstesting tests the stability of a given system or entity. It tests something beyond its normaloperational capacity, in order to observe any negative results. For example, a web server is stresstested, using scripts, bots, and various denial of service tools.

Q77. What is load testing?

A: Load testing simulates the expected usage of a software program, by simulating multiple usersthat access the program's services concurrently. Load testing is most useful and most relevant formulti-user systems, client/server models, including web servers. For example, the load placed on

the system is increased above normal usage patterns, in order to test the system's response atpeak loads. You CAN learn load testing, with little or no outside help. Get CAN get free information.Click on a link!

Q79. What is the difference between performance testing andload testing?

A: Load testing is a blanket term that is used in many different ways across the


20/34

professional software testing community. The term, load testing, is often usedsynonymously with stress testing, performance testing, reliability testing, and volumetesting. Load testing generally stops short of stress testing. During stress testing, the loadis so great that errors are the expected results, though there is gray area in between stresstesting and load testing. You CAN learn testing, with little or no outside help. Get CAN getfree information. Click on a link!

Q80. What is the difference between reliability testing andload testing?

A: Load testing is a blanket term that is used in many different ways across theprofessional software testing community. The term, load testing, is often usedsynonymously with stress testing, performance testing, reliability testing, and volumetesting. Load testing generally stops short of stress testing. During stress testing, the loadis so great that errors are the expected results, though there is gray area in between stresstesting and load testing.

Q81. What is the difference between volume testing and loadtesting?

A: Load testing is a blanket term that is used in many different ways across theprofessional software testing community. The term, load testing, is often usedsynonymously with stress testing, performance testing, reliability testing, and volumetesting. Load testing generally stops short of stress testing. During stress testing, the loadis so great that errors are the expected results, though there is gray area in between stresstesting and load testing.

Q82. What is incremental testing?

A: Incremental testing is partial testing of an incomplete product. The goal of incrementaltesting is to provide an early feedback to software developers.

Q83. What is software testing?

A: Software testing is a process that identifies the correctness, completenes, and quality ofsoftware. Actually, testing cannot establish the correctness of software. It can find defects,but cannot prove there are no defects. You CAN learn software testing, with little or nooutside help. Get CAN get free information. Click on a link!

Q84. What is automated testing?

A:Automated testing is a formally specified and controlled method of formal testingapproach.

Q85. What is alpha testing?A:Alpha testing is final testing before the software is released to the general public. First,(and this is called the first phase of alpha testing), the software is tested by in-housedevelopers. They use either debugger software, or hardware-assisted debuggers. The goalis to catch bugs quickly. Then, (and this is called second stage of alpha testing), thesoftware is handed over to us, the software QA staff, for additional testing in anenvironment that is similar to the intended use.


21/34

Q86. What is beta testing?

A: Following alpha testing, "beta versions" of the software are released to a group ofpeople, and limited public tests are performed, so that further testing can ensure theproduct has few bugs. Other times, beta versions are made available to the general public,in order to receive as much feedback as possible. The goal is to benefit the maximumnumber of future users.

Q87. What is the difference between alpha and beta testing?

A:Alpha testing is performed by in-house developers and software QA personnel. Betatesting is performed by the public, a few select prospective customers, or the generalpublic.

Q88. What is clear box testing?

A: Clear box testing is the same as white box testing. It is a testing approach thatexamines the application's program structure, and derives test cases from the application'sprogram logic. You CAN learn clear box testing, with little or no outside help. Get CAN getfree information. Click on a link!

Q89. What is boundary value analysis?

A: Boundary value analysis is a technique for test data selection. A test engineer choosesvalues that lie along data extremes. Boundary values include maximum, minimum, justinside boundaries, just outside boundaries, typical values, and error values. Theexpectation is that, if a systems works correctly for these extreme or special values, then itwill work correctly for all values in between. An effective way to test code, is to exercise itat its natural boundaries.

Q90. What is ad hoc testing?

A:Ad hoc testing is a testing approach; it is the least formal testing approach.

Q91. What is gamma testing?

A: Gamma testing is testing of software that has all the required features, but it did not gothrough all the in-house quality checks. Cynics tend to refer to software releases as"gamma testing".

Q92. What is glass box testing?

A: Glass box testing is the same as white box testing. It is a testing approach thatexamines the application's program structure, and derives test cases from the application'sprogram logic.

Q93. What is open box testing?

A: Open box testing is same as white box testing. It is a testing approach that examinesthe application's program structure, and derives test cases from the application's programlogic.


22/34

Q94. What is black box testing?

A: Black box testing a type of testing that considers only externally visible behavior. Blackbox testing considers neither the code itself, nor the "inner workings" of the software. YouCAN learn to do black box testing, with little or no outside help. Get CAN get freeinformation. Click on a link!

Q95. What is functional testing?

A: Functional testing is same as black box testing. Black box testing a type of testing thatconsiders only externally visible behavior. Black box testing considers neither the codeitself, nor the "inner workings" of the software.

Q96. What is closed box testing?

A: Closed box testing is same as black box testing. Black box testing a type of testing thatconsiders only externally visible behavior. Black box testing considers neither the codeitself, nor the "inner workings" of the software.

Q97. What is bottom-up testing?

A: Bottom-up testing is a technique for integration testing. A test engineer creates anduses test drivers for components that have not yet been developed, because, with bottom-up testing, low-level components are tested first. The objective of bottom-up testing is tocall low-level components first, for testingpurposes.

Q98. What is software quality?

A: The quality of the software does vary widely from system to system. Some commonquality attributes are stability, usability, reliability, portability, and maintainability. Seequality standard ISO 9126 for more information on this subject

Q99. How do test case templates look like?

A: Software test cases are in a document that describes inputs, actions, or events, andtheir expected results, in order to determine if all features of an application are workingcorrectly. Test case templates contain all particulars of every test case. Often thesetemplates are in the form of a table. One example of this table is a 6-column table, wherecolumn 1 is the "Test Case ID Number", column 2 is the "Test Case Name", column 3 isthe "Test Objective", column 4 is the "Test Conditions/Setup", column 5 is the "Input DataRequirements/Steps", and column 6 is the "Expected Results". All documents should bewritten to a certain standard and template. Standards and templates maintain documentuniformity. They also help in learning where information is located, making it easier for

users to find what they want. Lastly, with standards and templates, information will not beaccidentally omitted from a document. You CAN learn to create test case templates, withlittle or no outside help. Get CAN get free information. Click on a link!

Q100. What is a software fault?

A: Software faults are hidden programming errors. Software faults are errors in thecorrectness of the semantics of computer programs.


23/34

Q101. What is software failure?

A:A software failure occurs when the software does not do what the user expects to see.

Q102. What is the difference between a software fault and asoftware failure?

A:A software failure occurs when the software does not do what the user expects to see.A software fault, on the other hand, is a hidden programming error. A software faultbecomes a software failure only when the exact computation conditions are met, and thefaulty portion of the code is executed on the CPU. This can occur during normal usage. Or,when the software is ported to a different hardware platform. Or, when the software isported to a different complier. Or, when the software gets extended.

Q103. What is a test engineer?

A: Test engineers are engineers who specialize in testing. We, test engineers, create testcases, procedures, scripts and generate data. We execute test procedures and scripts,

analyze standards of measurements, evaluate results of system/integration/regressiontesting.

Q104. What is the role of test engineers?

A: Test engineers speed up the work of the development staff, and reduce the risk of yourcompany's legal liability. We, test engineers, also give the company the evidence that thesoftware is correct and operates properly. We also improve problem tracking and reporting,maximize the value of the software, and the value of the devices that use it. We alsoassure the successful launch of the product by discovering bugs and design flaws, before...

users get discouraged, before shareholders loose their cool and before employees get

bogged down. We, test engineers help the work of software development staff, so thedevelopment team can devote its time to build up the product. We, test engineers alsopromote continual improvement. They provide documentation required by FDA, FAA, otherregulatory agencies, and your customers. We, test engineers save your company moneyby discovering defects EARLY in the design process, before failures occur in production, orin the field. We save the reputation of your company by discovering bugs and design flaws,before bugs and design flaws damage the reputation of your company.

Q105. What is a QA engineer?

A: QA engineers are test engineers, but QA engineers do more than just testing. Good QAengineers understand the entire software development process and how it fits into thebusiness approach and the goals of the organization. Communication skills and the ability

to understand various sides of issues are important. We, QA engineers, are successful ifpeople listen to us, if people use our tests, if people think that we're useful, and if we'rehappy doing our work. I would love to see QA departments staffed with experiencedsoftware developers who coach development teams to write better code. But I've neverseen it. Instead of coaching, we, QA engineers, tend to be process people.


24/34

Q106. What metrics are used for bug tracking?

A: Metrics that can be used for bug tracking include: total number of bugs, total number ofbugs that have been fixed, number of new bugs per week, and number of fixes per week.Metrics for bug tracking can be used to determine when to stop testing, e.g. when bug ratefalls below a certain level. You CAN learn to use defect tracking software, with little or nooutside help. Get CAN get free information. Click on a link!

Q107. What is role of the QA engineer?

A: The QA Engineer's function is to use the system much like real users would, find all thebugs, find ways to replicate the bugs, submit bug reports to the developers, and to providefeedback to the developers, i.e. tell them if they've achieved the desired level of quality.

Q108. What are the responsibilities of a QA engineer?

A: Let's say, an engineer is hired for a small software company's QA role, and there is no

QA team. Should he take responsibility to set up a QA infrastructure/process, testing andquality of the entire product? No, because taking this responsibility is a classic trap that QApeople get caught in. Why? Because we QA engineers cannot assure quality. And becauseQA departments cannot create quality. What we CAN do is to detect lack of quality, andprevent low-quality products from going out the door. What is the solution? We need todrop the QA label, and tell the developers, they are responsible for the quality of their ownwork. The problem is, sometimes, as soon as the developers learn that there is a testdepartment, they will slack off on their testing. We need to offer to help with qualityassessment only.

Q109. What metrics can be used in software development?

A: Metrics refer to statistical process control. The idea of statistical process control is a

great one, but it has only a limited use in software development. On the negative side,statistical process control works only with processes that are sufficiently well defined ANDunvaried, so that they can be analyzed in terms of statistics. The problem is, most softwaredevelopment projects are NOT sufficiently well defined and NOT sufficiently unvaried. Onthe positive side, one CAN use statistics. Statistics are excellent tools that projectmanagers can use. Statistics can be used, for example, to determine when to stop testing,i.e. test cases completed with certain percentage passed, or when bug rate falls below acertain level. But, if these are project management tools, why should we label them qualityassurance tools?

Q110. How do you perform integration testing?

A: First, unit testing has to be completed. Upon completion of unit testing, integrationtesting begins. Integration testing is black box testing. The purpose of integration testing isto ensure distinct components of the application still work in accordance to customerrequirements. Test cases are developed with the express purpose of exercising theinterfaces between the components. This activity is carried out by the test team. Integrationtesting is considered complete, when actual results and expected results are either in lineor differences are explainable/acceptable based on client input. You CAN learn to performintegration testing, with little or no outside help. Get CAN get free information. Click on alink!


25/34

Q111. What is integration testing?

A: Integration testing is black box testing. The purpose of integration testing is to ensuredistinct components of the application still work in accordance to customer requirements.Test cases are developed with the express purpose of exercising the interfaces betweenthe components. This activity is carried out by the test team. Integration testing isconsidered complete, when actual results and expected results are either in line or

differences are explainable/acceptable based on client input.

Q112. What metrics are used for test report generation?

A: Metrics refer to statistical process control. The idea of statistical process control is a great one,but it has only a limited use in software development.On the negative side, statistical process control works only with processes that are sufficiently welldefined AND unvaried, so that they can be analyzed in terms of statistics. The problem is, mostsoftware development projects are NOT sufficiently well defined and NOT sufficiently unvaried.

On the positive side, one CAN use statistics. Statistics are excellent tools that project managerscan use. Statistics can be used, for example, to determine when to stop testing, i.e. test cases

completed with certain percentage passed, or when bug rate falls below a certain level. But, if theseare project management tools, why should we label them quality assurance tools?

The followings describe some of the metrics in quality assurance:

McCabe Metrics

Cyclomatic Complexity Metric (v(G)). Cyclomatic Complexity is a measure of thecomplexity of a module's decision structure. It's the number of linearly independent pathsand therefore, the minimum number of paths that should be tested.

Actual Complexity Metric (AC). Actual Complexity is the number of independent pathstraversed during testing.

Module Design Complexity Metric (iv(G)). Module Design Complexity is the complexity of

the design-reduced module, and reflects the complexity of the module's calling patterns toits immediate subordinate modules. This metric differentiates between modules thatseriously complicate the design of a program they are part of, and modules that simplycontain complex computational logic. It is the basis upon which program design andintegration complexities (S0 and S1) are calculated.

Essential Complexity Metric (ev(G)). Essential Complexity is a measure of the degree towhich a module contains unstructured constructs. This metric measures the degree ofstructuredness and the quality of the code. This metric is used to predict the requiredmaintenance effort and to help in the modularization process.

Pathological Complexity Metric (pv(G)). Pathological Complexity Metric is a measure of thedegree to which a module contains extremely unstructured constructs.

Design Complexity Metric (S0). Design Complexity Metric measures the amount ofinteraction between modules in a system.

Integration Complexity Metric (S1). Integration Complexity Metric measures the amount ofintegration testing necessary to guard against errors.

Object Integration Complexity Metric (OS1). Object Integration Complexity Metric quantifiesthe number of tests necessary to fully integrate an object or class into an OO system.

Global Data Complexity Metric (gdv(G)). Global Data Complexity Metric quantifies thecyclomatic complexity of a module's structure as it relates to global/parameter data. It canbe no less than one and no more than the cyclomatic complexity of the original flowgraph.

McCabe Data-Related Software Metrics


26/34

Data Complexity Metric (DV). Data Complexity Metric quantifies the complexity of amodule's structure as it relates to data-related variables. It is the number of independentpaths through data logic, and therefore, a measure of the testing effort with respect to data-related variables.

Tested Data Complexity Metric (TDV). Tested Data Complexity Metric quantifies thecomplexity of a module's structure as it relates to data-related variables. It is the number ofindependent paths through data logic that have been tested.

Data Reference Metric (DR). Data Reference Metric measures references to data-relatedvariables independently of control flow. It is the total number of times that data-relatedvariables are used in a module.

Tested Data Reference Metric (TDR). Tested Data Reference Metric is the total number oftested references to data-related variables.

Maintenance Severity Metric (maint_severity). Maintenance Severity Metric measures howdifficult it is to maintain a module.

Data Reference Severity Metric (DR_severity). Data Reference Severity Metric measuresthe level of data intensity within a module. It is an indicator of high levels of data relatedcode; therefore, a module is data intense if it contains a large number of data-relatedvariables.

Data Complexity Severity Metric (DV_severity). Data Complexity Severity Metric measuresthe level of data density within a module. It is an indicator of high levels of data logic in test

paths, therefore, a module is data dense if it contains data-related variables in a largeproportion of its structures.

Global Data Severity Metric (gdv_severity). Global Data Severity Metric measures thepotential impact of testing data-related basis paths across modules. It is based on globaldata test paths.

McCabe Object-Oriented Software Metrics; Encapsulation

Percent Public Data (PCTPUB). PCTPUB is the percentage of public and proteceddata within a class.

Access to Public Data (PUBDATA) PUBDATA indicates the number of accesses topublic and protected data.

McCabe Object-Oriented Software Metrics; Polymorphism

Percent of Unoverloaded Calls (PCTCALL). PCTCALL is the number of non-overloaded calls in a system.

Number of Roots (ROOTCNT). ROOTCNT is the total number of class hierarchyroots within a program.

Fan-in (FANIN). FANIN is the number of classes from which a class is derived.

McCabe Object-Oriented Software Metrics; Quality

Maximum v(G) (MAXV). MAXV is the maximum cyclomatic complexity value forany single method within a class.

Maximum ev(G) (MAXEV). MAXEV is the maximum essential complexity value forany single method within a class.

Hierarchy Quality(QUAL). QUAL counts the number of classes within a system thatare dependent upon their descendants.

Other Object-Oriented Software Metrics


27/34

Depth (DEPTH). Depth indicates at what level a class is located within its classhierarchy.

Lack of Cohesion of Methods (LOCM). LOCM is a measure of how the methods ofa class interact with the data in a class.

Number of Children (NOC). NOC is the number of classes that are derived directlyfrom a specified class.

Response For a Class (RFC). RFC is a count of methods implemented within a

class plus the number of methods accessible to an object of this class type due toinheritance.

Weighted Methods Per Class (WMC). WMC is a count of methods implementedwithin a class.

Halstead Software Metrics

Program Length. Program length is the total number of operator occurences andthe total number of operand occurences.

Program Volume. Program volume is the minimum number of bits required forcoding the program.

Program Level and Program Difficulty. Program level and program difficulty is ameasure of how easily a program is comprehended.

Intelligent Content. Intelligent content shows the complexity of a given algorithmindependent of the language used to express the algorithm.

Programming Effort. Programming effort is the estimated mental effort required todevelop a program.

Error Estimate. Error estimate calculates the number of errors in a program.

Programming Time. Programming time is the estimated amount of time toimplement an algorithm.

Line Count Software Metrics

Lines of Code

Lines of Comment

Lines of Mixed Code and Comments Lines Left Blank

Q113. How do test plan templates look like?

A: The test plan document template helps to generate test plan documents that describethe objectives, scope, approach and focus of a software testing effort. Test documenttemplates are often in the form of documents that are divided into sections andsubsections. One example of this template is a 4-section document, where section 1 is thedescription of the "Test Objective", section 2 is the the description of "Scope of Testing",section 3 is the the description of the "Test Approach", and section 4 is the "Focus of theTesting Effort". All documents should be written to a certain standard and template.

Standards and templates maintain document uniformity. They also help in learning whereinformation is located, making it easier for a user to find what they want. With standardsand templates, information will not be accidentally omitted from a document. Once RobDavis has learned and reviewed your standards and templates, he will use them. He willalso recommend improvements and/or additions. A software project test plan is adocument that describes the objectives, scope, approach and focus of a software testingeffort. The process of preparing a test plan is a useful way to think through the effortsneeded to validate the acceptability of a software product. The completed document willhelp people outside the test group understand the why and how of product validation. YouCAN learn to generate test plan templates, with little or no outside help. Get CAN get free


28/34

information. Click on a link!

Q114. What is a "bug life cycle"?

A: Bug life cycles are similar to software development life cycles. At any time during thesoftware development life cycle errors can be made during the gathering of requirements,requirements analysis, functional design, internal design, documentation planning,document preparation, coding, unit testing, test planning, integration, testing, maintenance,updates, re-testing and phase-out. Bug life cycle begins when a programmer, softwaredeveloper, or architect makes a mistake, creates an unintentional software defect, i.e. abug, and ends when the bug is fixed, and the bug is no longer in existence. What should bedone after a bug is found? When a bug is found, it needs to be communicated andassigned to developers that can fix it. After the problem is resolved, fixes should be re-tested. Additionally, determinations should be made regarding requirements, software,hardware, safety impact, etc., for regression testing to check the fixes didn't create otherproblems elsewhere. If a problem-tracking system is in place, it should encapsulate thesedeterminations. A variety of commercial, problem-tracking/management software tools areavailable. These tools, with the detailed input of software test engineers, will give the teamcomplete information so developers can understand the bug, get an idea of its severity,reproduce it and fix it.

Q115. When do you choose automated testing?

A: For larger projects, or ongoing long-term projects, automated testing can be valuable.But for small projects, the time needed to learn and implement the automated testing toolsis usually not worthwhile. Automated testing tools sometimes do not make testing easier.One problem with automated testing tools is that if there are continual changes to theproduct being tested, the recordings have to be changed so often, that it becomes a verytime-consuming task to continuously update the scripts. Another problem with such tools isthe interpretation of the results (screens, data, logs, etc.) that can be a time-consumingtask. You CAN learn to use automated tools, with little or no outside help. Get CAN get freeinformation. Click on a link!

Q116. What is the ratio of developers and testers?

A: This ratio is not a fixed one, but depends on what phase of the software developmentlife cycle the project is in. When a product is first conceived, organized, and developed, thisratio tends to be 10:1, 5:1, or 3:1, i.e. heavily in favor of developers. In sharp contrast,when the product is near the end of the software development life cycle, this ratio tends tobe 1:1, or even 1:2, in favor of testers.

Q117. What is your role in your current organization?

A: I'm a Software QA Engineer. I use the system much like real users would. I find all the

bugs, find ways to replicate the bugs, submit bug reports to developers, and providesfeedback to the developers, i.e. tell them if they've achieved the desired level of quality.

Q118. Should I take a course in manual testing?

A: Learning how to perform manual testing is an important part of one's education. I see noreason why one should skip an important part of an academic program.


29/34

Q119. How can I learn to use WinRunner, without any outsidehelp?

A: I suggest you read all you can, and that includes reading product description pamphlets,manuals, books, information on the Internet, and whatever information you can lay yourhands on. Then the next step is getting some hands-on experience on how to use

WinRunner. If there is a will, there is a way! You CAN do it, if you put your mind to it! YouCAN learn to use WinRunner, with little or no outside help. Get CAN get free information.Click on a link!

Q120. To learn to use WinRunner, should I sign up for acourse at a nearby educational institution?

A: The cheapest, or free, education is sometimes provided on the job, by an employer,while one is getting paid to do a job that requires the use of WinRunner and many othersoftware testing tools. In lieu of a job, it is often a good idea to sign up for courses atnearby educational institutions. Classroom education, especially non-degree courses inlocal, community colleges, tends to be cheap.

Q121. I don't have a lot of money. How can I become a goodtester with little or no cost to me?

A: The cheapest, or free, education is sometimes provided on the job, by an employer,while one is getting paid to do a job that requires the use of WinRunner and many othersoftware testing tools.

Q122. What software tools are in demand these days?A: The software tools currently in demand include LabView, LoadRunner, Rational Tools,and Winrunner -- and especially the Loadrunner and Rational Toolset -- but there are manyothers, depending on the end client, and their needs, and preferences.

Q123. Which of these tools should I learn?

A: I suggest you learn the most popular software tools (i.e. LabView, LoadRunner, RationalTools, Winrunner, etc.) -- and you want to pay special attention to LoadRunner and theRational Toolset.

Q124. What are some of the software configurationmanagement tools?

A: Software configuration management tools include Rational ClearCase, DOORS, PVCS,CVS; and there are many others. Rational ClearCase is a popular software tool, made byRational Software, for revision control of source code. DOORS, or "Dynamic ObjectOriented Requirements System", is a requirements version control software tool. CVS, or"Concurrent Version System", is a popular, open source version control system to keeptrack of changes in documents associated with software projects. CVS enables several,often distant, developers to work together on the same source code. PVCS is a documentversion control tool, a competitor of SCCS. SCCS is an original UNIX program, based on"diff". Diff is a UNIX command that compares contents of two files. You CAN learn to useSCM tools, with little or no outside help. Get CAN get free information. Click on a link!

Q125. What is software configuration management?


30/34

A: Software Configuration management (SCM) is the control, and the recording of,changes that are made to the software and documentation throughout the softwaredevelopment life cycle (SDLC). SCM covers the tools and processes used to control,coordinate and track code, requirements, documentation, problems, change requests,designs, tools, compilers, libraries, patches, and changes made to them, and to keep trackof who makes the changes. Rob Davis has experience with a full range of CM tools and

concepts, and can easily adapt to an organization's software tool and process needs.

Q126. What other roles are in testing?

A: Depending on the organization, the following roles are more or less standard on mosttesting projects: Testers, Test Engineers, Test/QA Team Leads, Test/QA Managers,System Administrators, Database Administrators, Technical Analysts, Test BuildManagers, and Test Configuration Managers. Depending on the project, one person canand often wear more than one hat. For instance, we Test Engineers often wear the hat ofTechnical Analyst, Test Build Manager and Test Configuration Manager as well.

Q127. Which of these roles are the best and most popular?

A:As a yardstick of popularity, if we count the number of applicants and resumes, Testerroles tend to be the most popular. Less popular roles are roles of System Administrators,Test/QA Team Leads, and Test/QA Managers. The "best" job is the job that makes YOUhappy. The best job is the one that works for YOU, using the skills, resources, and talentsYOU have. To find the best job, you need to experiment, and "play" different roles.Persistence, combined with experimentation, will lead to success.

Q128. What's the difference between priority and severity?

A: "Priority" is associated with scheduling, and "severity" is associated with standards."Piority" means something is afforded or deserves prior attention; a precedence

established by order of importance (or urgency). "Severity" is the state or quality of beingsevere; severe implies adherence to rigorous standards or high principles and oftensuggests harshness; severe is marked by or requires strict adherence to rigorousstandards or high principles, e.g. a severe code of behavior. The words priority andseverity do come up in bug tracking. A variety of commercial, problem-tracking/management software tools are available. These tools, with the detailed input ofsoftware test engineers, give the team complete information so developers can understandthe bug, get an idea of its 'severity', reproduce it and fix it. The fixes are based on project'priorities' and 'severity' of bugs. The 'severity' of a problem is defined in accordance to thecustomer's risk assessment and recorded in their selected tracking tool. A buggy softwarecan 'severely' affect schedules, which, in turn can lead to a reassessment andrenegotiation of 'priorities'.

Q129. What's the difference between efficient and effective?

A: "Efficient" means having a high ratio of output to input; working or producing with aminimum of waste. For example, "An efficient engine saves gas". "Effective", on the otherhand, means producing, or capable of producing, an intended result, or having a strikingeffect. For example, "For rapid long-distance transportation, the jet engine is more effectivethan a witch's broomstick".


31/34

Q130. What is the difference between verification andvalidation?

A: Verification takes place before validation, and not vice versa. Verification evaluatesdocuments, plans, code, requirements, and specific

Testin Faqs

Documents

Transcript of Testin Faqs