“Software Quality Control frequently Asked Questions by expert members with experience in Software Quality Control. These questions and answers will help you strengthen your technical skills, prepare for the new job test and quickly revise the concepts”
How would you categorize the severity of defects?
Where do you imagine you will be spending the bulk of your time?
When do you know you have tested enough?
What types of documents would you need for QA, QC, and Testing?
What did you include in a test plan?
Describe any bug you remember.
What is the purpose of the testing?
What do you like (not like) in this job?
What is quality assurance?
What is the difference between QA and testing?
Tell me about any quality efforts you have overseen or implemented. Describe some of the challenges you faced and how you overcame them.
How do you deal with environments that are hostile to quality change efforts?
In general, how do you see automation fitting into the overall process of testing?
How do you promote the concept of phase containment and defect prevention?
If you come onboard, give me a general idea of what your first overall tasks will be as far as starting a quality effort.
What kinds of testing have you done?
Have you ever created a test plan?
Have you ever written test cases or did you just execute those written by others?
What did your base your test cases?
You are the test manager starting on system testing. The development team says that due to a change in the requirements, they will be able to deliver the system for SQA 5 days past the deadline. You cannot change the resources (work hours, days, or test tools). What steps will you take to be able to finish the testing in time?
How do you scope, organize, and execute a test project?
What is the role of QA in a development project?
What is the role of QA in a company that produces software?
Define quality for me as you understand it
Describe to me the difference between validation and verification.
Describe to me what you see as a process. Not a particular process, just the basics of having a process.
Describe to me when you would consider employing a failure mode and effect analysis.
Describe to me the Software Development Life Cycle as you would define it.
What are the properties of a good requirement?
How do you differentiate the roles of Quality Assurance Manager and Project Manager?
Your company is about to roll out an e-commerce application. It’s not possible to test the application on all types of browsers on all platforms and operating systems. What steps would you take in the testing environment to reduce the business risks and commercial risks?
In your organization, testers are delivering code for system testing without performing unit testing. Give an example of test policy:
Policy statement
Methodology
Measurement
Testers in your organization are performing tests on the deliverables even after significant defects have been found. This has resulted in unnecessary testing of little value, because re-testing needs to be done after defects have been rectified. You are going to update the test plan with recommendations on when to halt testing. Wwhat recommendations are you going to make?
How do you measure:
Test Effectiveness
Test Efficiency
You found out the senior testers are making more mistakes then junior testers; you need to communicate this aspect to the senior tester. Also, you don’t want to lose this tester. How should one go about constructive criticism?
You are assigned to be the test lead for a new program that will automate take-offs and landings at an airport. How would you write a test strategy for this new program?
- Quality Control Plan is to analyze the operations needed for the fulfillment of the software project requirements.
- Quality Control Plan ensures all the specifications are met and the quality of the product is maintained
The characteristics of the Quality Plan are as follows:
- Consistent: The plan should adhere to the guidelines and the specific standards.
- Complete: The plan should include project requirements, features and essentially the project plan documentation.
- Clear: The plan should be transparent to the developer and also to all the stake holders of the project requirements.
- Correct: The details of the project should be very clear to all stakeholders about project delivery date / postponement / cancellation.
A set of activities for ensuring the quality of the software product is known as Software Quality Control.
The focus is on identifying the defects in the original products produced.
It is limited only for Testing phase of SDLC.
Software Quality Control is governed by Software Quality Assurance.
Software Quality Control is detection oriented.
The scope relates to specific product.
Software Quality Control Nomenclature:
- Verifying: comparing the code predictions
- Validating: Comparing the prediction of code with test data
- Version Testing: Comparing output of the current version with output of the previous version
- Installation Testing: Comparing the result with newly installed code to the sample result code
- Development Code: Code tested only by the software developer.
- Alpha Code: Testing of the software product internally by selected users.
- Beta Code: Code testing internally by a large numbers of users.
- Released Code: Well tested and documented code that is officially distributed.
- Functionality - To determine the required functionality in the software
- Usability – To determine the ease of the software is to use.
- Maintainability – To determine whether the modifications of the software can be made.
- Efficiency - To determine whether the software is efficient.
- Portability – To determine whether the software can be transferred to another environment.
- Reliability – To determine the reliability of the software as per the client’s needs.
- Functionality : Functions that satisfies the specified requirements.
- Reliability : A set of attributes that are capable of software maintenance under specified conditions.
- Usability : A set of attributes that is capable of effort bearing on individual’s performance.
- Efficiency: A set of attributes that are capable of balancing the relationship between performance of software and the resources used.
- Maintainability: A set of attributes that are capable of bearing the effort required for specific modifications.
- Portability: A set of attributes those are capable to bear on the ability of the software to be transferred on another environment.
- Clear purpose of the product. All documentation must be clearly written.
- Completeness to the fullest development of the product.
- Only needed information and minimum lines of code should present. It is important as the memory is limited.
- The software product should be portable, so that computers of various configurations would support the execution of the product.
- Product should be maintainable, so that the updating activity can be continued throughout the life time of the software product.
- A paradigm that is Goal Question centric.
- A method that control the overall risk.
- Quality Control that involves Plan, Perform, Check, Action Model.
- Complete Software Quality Control.
- Software Development Method that involve the Spiral Model.
- Focused on planning, documentation and agreeing certain guidelines that ensures quality.
- The outcomes of Quality Assurance are quality plans, inspection plan, test plan.
- QA is to prevent defects from entering into solutions.
Quality Assurance:
- Focused on planning, documentation and agreeing certain guidelines that ensures quality.
- The outcomes of Quality Assurance are quality plans, inspection plan, test plan.
- QA is to prevent defects from entering into solutions.
Quality Control:
- Includes the activities that are designed to determine the level of quality.
- QC is a reactive means which measures and monitors the quality
- Includes operational activities and techniques to meet the quality needs.
- QC involves in verifying the desired quality levels.
- Includes the activities that are designed to determine the level of quality.
- QC is a reactive means which measures and monitors the quality
- Includes operational activities and techniques to meet the quality needs.
- QC involves in verifying the desired quality levels.
The following are the SE Practices and attributes:
- Coding practices / standards.
- Practices of Application Architecture.
- Determining the complexity of the algorithms.
- Determining the multi-layer design compliance.
- Ratio of component and pattern usability.
- Determining the software to avoid the patterns which would lead to unexpected results / behaviors.
- Determination of data integrity and consistency.
- Implementing proper Application Architecture Practices.
- Design compliance of multi-layer components and their functionality.
- Input validation, Cross Site Scripting best practices
- Proper handling of error and exceptions.
- Proper access controls to the program and system functions.
- Practices of implementing Application Architecture.
- Interactions with remote resources should be appropriate.
- Proper management of memory, network and disk space.
- Best coding practices.
- Proper and appropriate data access performance and management.
- Appropriate compliance with Object Oriented and Structured Programming practices.
- Appropriate compliance with SQL Programming best practices.
- The most technical sizing method is measured in terms of Line of Code per technology.
- The number of lines include in functions, files, classes and tables.
- These are computed with backfiring the Function Points.
- The very common function size is Function Point Analysis.
- FPA is all about measuring the software deliverables.
- FPA is based on the requirements of the user and presents accurate representation of developer and estimator.
- FPA reflects the functionality that is delivered to the client.
- FPA involves in identifying and weighting of inputs, outputs and data storage.
There are two types of software sizes:
Technical Size:
- The most technical sizing method is measured in terms of Line of Code per technology.
- The number of lines include in functions, files, classes and tables.
- These are computed with backfiring the Function Points.
Functional Size:
- The very common function size is Function Point Analysis.
- FPA is all about measuring the software deliverables.
- FPA is based on the requirements of the user and presents accurate representation of developer and estimator.
- FPA reflects the functionality that is delivered to the client.
- FPA involves in identifying and weighting of inputs, outputs and data storage.
rendc.org
Whether it is technological solutions or user-oriented innovations, We have put together for you the best sources of HR Interview Questions and Answers, Tech Ideas, and Programming Tutorials."
Get all the latest information on rendc.org
© 2022 | All rights reserved.
RENDC
welcome to www.rendc.org
