FAQ'S security Testing

Q170. How do you check the security of your application?
A: To check the security of an application, we can use security/penetration testing. Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.
Q171. How do you test the password field?
A: To test the password field, we do boundary value testing.
Q172. When testing the password field, what is your focus?
A: When testing the password field, one needs to verify that passwords are encrypted.
Q173. What stage of bug fixing is the most cost effective?
A: Bug prevention, i.e. inspections, PDRs, and walk-throughs, is more cost effective than bug detection.

Q174. What is the objective of regression testing?
A: The objective of regression testing is to test that the fixes have not created any other problems elsewhere. In other words, the objective is to ensure the software has remained intact. A baseline set of data and scripts are maintained and executed, to verify that changes introduced during the release have not "undone" any previous code. Expected results from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.
Q175. What types of white box testing can you tell me about?
A: White box testing is a testing approach that examines the application's program structure, and derives test cases from the application's program logic. Clear box testing is a white box type of testing. Glass box testing is also a white box type of testing. Open box testing is also a white box type of testing.
Q176. What types of black box testing can you tell me about?
A: Black box testing is functional testing, not based on any knowledge of internal software design or code. Black box testing is based on requirements and functionality. Functional testing is also a black-box type of testing geared to functional requirements of an application. System testing is also a black box type of testing. Acceptance testing is also a black box type of testing. Functional testing is also a black box type of testing. Closed box testing is also a black box type of testing. Integration testing is also a black box type of testing.
Q177. Is the regression testing performed manually?
A: It depends on the initial testing approach. If the initial testing approach is manual testing, then, usually the regression testing is performed manually. Conversely, if the initial testing approach is automated testing, then, usually the regression testing is performed by automated testing. Q178. Please give me others' FAQs on testing.
A: Visit my web site, and on pages www.robdavispe.com/free and www.robdavispe.com/free2 you can find answers to the vast majority of other testers' FAQs on testing, from a tester's point of view. As to questions and answers that are not on my web site now, please be patient, as I am going to add more FAQs, as soon as time permits.
Q179. Can you share with me your knowledge of software testing?
A: Surely I can. For my knowledge on software testing, visit my web site, www.robdavispe.com/free and www.robdavispe.com/free2. As to knowledge that is not on my web site at the moment, please be patient, as I am going to add more answers, as soon as time permits.
Q180. How can I learn software testing?
A: I suggest you visit my web site, www.robdavispe.com/free and www.robdavispe.com/free2, and you will find answers to most questions on software testing. As to questions and answers that are not on my web site now, please be patient, as I am going to add more answers, as soon as time permits. I also suggest you get a job in software testing. Why? Because you can get additional, usually free, education on the job, while you are getting paid to do software testing. On the job you can use many software tools, including Winrunner, LoadRunner, LabView, and Rational Toolset. The selection of tools will depend on the end client, their needs, and preferences. I also suggest you sign up for courses at nearby educational institutes. Classroom education, especially non-degree courses in local community colleges, tends to be highly cost effective.

Q181. What is your view of software QA/testing?
A: Software QA/testing is easy, if requirements are solid, clear, complete, detailed, cohesive, attainable and testable, if schedules are realistic, and if there is good communication. Software QA/testing is a piece of cake, if project schedules are realistic, if adequate time is allowed for planning, design, testing, bug fixing, re-testing, changes, and documentation. Software QA/testing is easy, if testing is started early on, if fixes or changes are re-tested, and if sufficient time is planned for both testing and bug fixing. Software QA/testing is easy, if new features are avoided, if one is able to stick to initial requirements as much as possible.
Q182. How can I be a good tester?
A: We, good testers, take the customers' point of view. We are tactful and diplomatic. We have a "test to break" attitude, a strong desire for quality, an attention to detail, and good communication skills, both oral and written. Previous software development experience is also helpful as it provides a deeper understanding of the software development process.
Q183. What is the difference between a software bug and software defect?
A: A 'software bug' is a *nonspecific* term that means an inexplicable defect, error, flaw, mistake, failure, fault, or unwanted behavior of a computer program. Other terms, e.g. 'software defect' and 'software failure', are *more specific*. While the term bug has been a part of engineering jargon for many-many decades, there are many who believe the term 'bug' was named after insects that used to cause malfunctions in electromechanical computers.
Q184. How can I improve my career in software QA/testing?
A: Invest in your skills! Learn all you can! Visit my web site, and on www.robdavispe.com/free and www.robdavispe.com/free2 you will find answers to the vast majority of questions on testing, from software QA/testers' point of view. Get additional education, on the job. Free education is often provided by employers, while you are paid to do the job of a tester. On the job, often you can use many software tools, including WinRunner, LoadRunner, LabView, and Rational Toolset. Find an employer whose needs and preferences are similar to yours. Get an education! Sign up for courses at nearby educational institutes. Take classes! Classroom education, especially non-degree courses in local community colleges, tends to be inexpensive. Improve your attitude! Become the best software QA/tester! Always strive to exceed the expectations of your customers!
Q185. How do you compare two files?
A: Use PVCS, SCCS, or "diff". PVCS is a document version control tool, a competitor of SCCS. SCCS is an original UNIX program, based on "diff". Diff is a UNIX utility that compares the difference between two text files.
Q186. What do we use for comparison?
A: Generally speaking, when we write a software program to compare files, we compare two files, bit by bit. When we use "diff", a UNIX utility, we compare the difference between two text files.
Q187. What is the reason we compare files?
A: Configuration management, revision control, requirement version control, or document version control. Examples are Rational ClearCase, DOORS, PVCS, and CVS. CVS, for example, enables several, often distant, developers to work together on the same source code.
Q188. When is a process repeatable?
A: If we use detailed and well-written processes and procedures, we ensure the correct steps are being executed. This facilitates a successful completion of a task. This is a way we also ensure a process is repeatable.
Q189. What does a Test Strategy Document contain?
A: The test strategy document is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, and a list of related tasks, pass/fail criteria and risk assessment. Additional sections in the test strategy document include: A description of the required hardware and software components, including test tools. This information comes from the test environment, including test tool data. A description of roles and responsibilities of the resources required for the test and schedule 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 comes from requirements, change request, technical, and functional design documents. Requirements that the system cannot provide, e.g. system limitations.
Q190. What is test methodology?
A: One test methodology is a three-step process. Creating a test strategy, Creating a test plan/design, and Executing tests. This methodology can be used and molded to your organization's needs. Rob Davis believes that using this methodology is important in the development and ongoing maintenance of his customers' applications.
Q191. How can I start my career in Automated testing?
A: For one, 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 your hands on. Two, get hands-on experience on how to use automated testing tools. If there is a will, there is a way! You CAN do it, if you put your mind to it! You CAN learn to use WinRunner, and many other automated testing tools, with little or no outside help. Click on a link!

Previous Software FAQ'S             More Software FAQ'S