FAQ'S 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 many others, 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, Rational Tools, Winrunner, etc.) -- and you want to pay special attention to LoadRunner and the Rational Toolset.
Q124. What are some of the software configuration management 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 by Rational Software, for revision control of source code. DOORS, or "Dynamic Object Oriented Requirements System", is a requirements version control software tool. CVS, or "Concurrent Version System", is a popular, open source version control system to keep track 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 document version 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 use SCM tools, with little or no outside help. Get CAN get free information. Click on a link!
Q125. What is software configuration management?
A: Software Configuration management (SCM) is the control, and the recording of, changes that are made to the software and documentation throughout the software development 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 track of 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 most testing projects: Testers, Test Engineers, Test/QA Team Leads, Test/QA Managers, System Administrators, Database Administrators, Technical Analysts, Test Build Managers, and Test Configuration Managers. Depending on the project, one person can and often wear more than one hat. For instance, we Test Engineers often wear the hat of Technical 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, Tester roles 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 YOU happy. The best job is the one that works for YOU, using the skills, resources, and talents YOU 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 being severe; severe implies adherence to rigorous standards or high principles and often suggests harshness; severe is marked by or requires strict adherence to rigorous standards or high principles, e.g. a severe code of behavior. The words priority and severity do come up in bug tracking. A variety of commercial, problem-tracking/management software tools are available. These tools, with the detailed input of software test engineers, give the team complete information so developers can understand the 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 the customer's risk assessment and recorded in their selected tracking tool. A buggy software can 'severely' affect schedules, which, in turn can lead to a reassessment and renegotiation 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 a minimum of waste. For example, "An efficient engine saves gas". "Effective", on the other hand, means producing, or capable of producing, an intended result, or having a striking effect. For example, "For rapid long-distance transportation, the jet engine is more effective than a witch's broomstick".
Q130. What is the difference between verification and validation?
A: Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements, and specifications. Validation, on the other hand, evaluates the product itself. The inputs of verification are checklists, issues lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation, on the other hand, is the actual testing of an actual product. The output of verification is a nearly perfect set of documents, plans, specifications, and requirements document. The output of validation, on the other hand, is a nearly perfect, actual product.
Q131. What is documentation change management?
A: Documentation change management is part of configuration management (CM). 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 the changes. Rob Davis has had experience with a full range of CM tools and concepts. Rob Davis can easily adapt to your software tool and process needs.
Q132. What is up time?
A: Up time is the time period when a system is operational and in service. Up time is the sum of busy time and idle time.
Q133. What is upwardly compatible software?
A: Upwardly compatible software is compatible with a later or more complex version of itself. For example, an upwardly compatible software is able to handle files created by a later version of itself.

Q134. What is upward compression?
A: In software design, upward compression means a form of demodularization, in which a subordinate module is copied into the body of a superior module.
Q135. What is usability?
A: Usability means ease of use; the ease with which a user can learn to operate, prepare inputs for, and interpret outputs of a software product.
Q136. What is user documentation?
A: User documentation is a document that describes the way a software product or system should be used to obtain the desired results.
Q137. What is a user manual?
A: User manual is a document that presents information necessary to employ software or a system to obtain the desired results. Typically, what is described are system and component capabilities, limitations, options, permitted inputs, expected outputs, error messages, and special instructions.

Previous Software FAQ'S             More Software FAQ'S