21⟩ What is testability in test managing?
The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.
Test Manager
Home Management Test Manager
“Test Manager job preparation guide for freshers and experienced candidates. Number of Test Manager frequently asked questions(FAQs) asked in many interviews”
36 Test Manager Questions And Answers
22⟩ Describe coding?
The generation of source code.
23⟩ Describe metric?
A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.
24⟩ Describe bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.
25⟩ Describe debugging?
The process of finding and removing the causes of software failures.
26⟩ Describe baseline?
The point at which some deliverable produced during the software engineering process is put under formal change control.
27⟩ Describe automated testing?
Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
28⟩ Tell me about cyclomatic complexity?
A measure of the logical complexity of an algorithm, used in white-box testing.
29⟩ What is good code in test managing?
Good code is code that works, is bug free, and is readable and maintainable. Some organizations have coding 'standards' that all developers are supposed to adhere to, but everyone has different ideas about what's best, or what is too many or too few rules. There are also various theories and metrics, such as Maccabees Complexity metrics. It should be kept in mind that excessive use of standards and rules can stifle productivity and creativity. 'Peer reviews', 'buddy checks' code analysis tools, etc. can be used to check for problems and enforce standards.
For C and C++ coding, here are some typical ideas to consider in setting rules/standards; these may or may not apply to a particular situation:
- minimize or eliminate use of global variables.
30⟩ Tell me what is test procedure?
A document providing detailed instructions for the execution of one or more test cases.
31⟩ Explain functional decomposition?
A technique used during planning, analysis and design; creates a functional hierarchy for the software.
32⟩ Describe concurrency testing?
Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
33⟩ Tell me what is storage testing?
Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.
34⟩ Tell me why does software have bugs?
★ Miscommunication or no communication - as to specifics of what an application should or shouldn't do (the application's requirements).
★ Software complexity - the complexity of current software applications can be difficult to comprehend for anyone without experience in modern-day software development. Multi-tiered applications, client-server and distributed applications, data communications, enormous relational databases, and sheer size of applications have all contributed to the exponential growth in software/system complexity. programming errors - programmers, like anyone else, can make mistakes.
35⟩ Tell me what is basis path testing?
A white box test case design technique that uses the algorithmic flow of the program to design tests.
36⟩ Tell me what kinds of testing should be considered?
Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.
unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
