Unit 7 Test Electronic Components
Unit 7 Test Electronic Components
COMPONENTS
COMMON COMPENTENCIES UNIT 7
LEARNING OUTCOME
The test is commonly performed in two parts namely; power-off tests and power-on tests. The power-off test
is performed to detect shorts between traces and component leads, values of resistors in the circuit,
presence/absence of passive and analog components.
Evaluate the testing process.
7 STEPS TO ASSESSING YOUR TESTING PROCESS
Goals
The principal goals of an assessment process are 1) to support the development of a test process profile and the
determination of a maturity level; 2) to guide the organization in developing action plans for test process improvement;
3) to ensure the assessment is executed with efficient use of the organization’s resources; and 4) to guide the assessment
team in collecting, organizing, and analyzing the assessment data. A brief summary of the steps in the assessment
procedure follows.
1. Preparation. This includes selecting the assessment team, choosing the team leader(s), developing the assessment
plan, selecting the projects, and preparing the organizational units participating in the assessment.
2. Conducting the assessment. In this step, the team collects and records assessment information from interviews,
presentations, questionnaires, and relevant documents. A test management support system is very helpful for collecting
and organizing test process related data and for use in cross-checking data from multiple sources.
3. Reporting the assessment outputs. The assessment outputs include an assessment report, a maturity
level, and the assessment record. The assessment team prepares the assessment report, which gives a
summary of the state of the organizations’ testing process. The report also includes a summary of test
process strengths and weaknesses, as well as recommendations for improvements.
4. Analyzing the assessment report. The assessment team, along with management and software quality
managers, now uses the assessment report to identify and prioritize improvement goals. Quantitative test
process improvement targets need to be established in this phase. The targets should support the action plans
developed in the next step.
5. Action planning. Management teams and the assessment team work together to develop plans that focus
on high-priority improvements identified in the previous step. This team can include assessors,
management, software quality assurance staff, and/or opinion leaders chosen from the assessment
participants. The action plan describes specific activities, resources, and schedules needed to improve
existing practices and add missing.
6. Implementing improvement. After the action plans have been developed and approved they are applied to
selected pilot projects. The pilot projects need to be monitored and tracked to ensure of task progress and goal
achievement. Favorable results with the pilot projects set the stage for organizational adaptation of the new
process.
7. Follow-up. A follow-up is recommended 6 months after the initial assessment. This follow-up will gauge your
progress on the action plans. This should only take about half the time, since the only things that will be assessed
are the action plan and any new process that were implemented since the initial assessment.
How do you evaluate your testing methods and strategies?
Testing methods and strategies are essential for ensuring the quality, functionality, and reliability of software
products. However, how do you know if your testing approach is effective and efficient? How do you measure the
results and outcomes of your testing activities? How do you identify the areas for improvement and
optimization? In this article, we will discuss some of the ways you can evaluate your testing methods and
strategies using quality assurance metrics and indicators.