2018: Fundamentals of Testing

11. Test Planning and Test Monitoring and Control

But for now, the test planning is where we define the objectives of testing, decide what to test, who will do the testing, how they will do the testing, and define the specific test activities in order to meet the objectives. For how long can we consider the testing complete, which is called the exit criteria. This is when we will stop testing and submit a report to the stakeholders to decide if testing was enough or not. All these, within constraints imposed by the context of the project test blends, may be revisited based on feedback for monitoring and control activities. Next, test monitoring and control We will also talk more about test monitoring and control in the test management section. But for now, you need to know that test monitoring is the ongoing activity of comparingactual progress against the test plan using any test monitoring metrics defined in the test plan. If there are any deviations between what's actually happening and the plan, then we should do test control,which is taking any necessary action or actions to stay on track to meet the targets. Therefore, we need to undertake both planning and control throughout the test activities. Remember the exit criteria that were defined during test landing? Well, during test monitoring and control, we should always evaluate the exit criteria to see if we have met the exit criteria or not yet. Evaluating exit criteria is an activity where test execution results are assessed against the defined objectives. For example, the evaluation of exit criteria for testexecution as part of a given test level may include checking test results and logs against the specified coverage criteria, assessing the level of component or system quality based on test results and logs, and determining whether more tests are needed. For example, if tests originally intended to achieve a certain level of product risk coverage fail to do so, additional tests have to be written and executed. Tested progress against the plan and the states of the exit criteria are communicated to stakeholders in testprogress reports, including deviations from the plan and information to support any decision to stop testing. The test manager then will evaluate the test reports submitted by various testers and decide if we should stop testing or if testing in a specific area should continue or not. For example, if the criterion was that software performance speed was to be an eight-second bare web page transaction. If the speed is ten seconds, meaning that the criteria are not met, then there are two possible actions. The most likely option is to employ extra testing activities till we achieve the desired performance. The least likely is to change the exit criteria, which will require approval from the stakeholders in Azure Life Cycles. The exit criteria map to what's called the definition of done. Again, we will talk more about test monitoring and control in the test management section.

12. Test Analysis and Test Design

concerned with the fine detail of knowing what to test and breaking it into fine testable elements that we call test conditions. It's the activity during which general testing objectives are transformed into real test conditions. During test analysis, any information or documentation we have is analysed to identify testable features and define associated test conditions. One term we need to learn is "test basis." A test basis is any sort of documentation that we can use as a reference or base to know what to test. Again, we will talk more about this basis in the following section. Test analysis includes the following major activities: analysing and understanding any documentation that we will use for testing to make sure it's testable. Examples of test basis include requirement specifications such as business requirements, functional requirements, system requirements, user stories, epic use cases, or similar work products that specify desired functional or nonfunctional component or system behavior. Also, design and implementation information such as system or software architecture diagrams or documents,design specifications, call flows modelling diagrams, for example, UML or entity relationship diagrams, interfacespecifications, or similar worker products that specify component or system structure. We also have the implementation of the component or system itself, including code, database,metadata, queries, and interfaces. Risk Analysis Reports, which list all the items in the software that are risky and require more attention from us. Risky Analysis Reports may consider functional, non-functional, and structural aspects of a component or system. All those are examples of the test basis. While we are analysing the testabases, it will be a very good opportunity to evaluate the test items and test bases to identify defects of various types, such as ambiguities, something that is confusing to the reader and might be interpreted differently by different people or measures. Something is not mentioned inconsistencies, something that was mentioned in a way somewhere but also mentioned differently somewhere else in accuracy. Something is not accurate. A contradiction is a contradiction between two statements, a stronger kind of inconsistency between them. If two sentences are contradictory, then one must be true and the other must be false. But if they are inconsistent, then both could be false. Superfluous statements are unnecessary statements that add nothing to the meaning. Actually, it's a skill to read an article and find effects in it. Not everyone can do it. It's a skill, but it's also a science that can be taught. So I should consider making a course about it, but I need to see students like you actually asking for it. It should be called Requirements Testing, so if you're interested, just shout out in the Questions and Answers section. The identification of defects during test analysis is a significant potential benefit, especially where no other review process is being used and or the test process is closely connected with the review process. After analyzing, understanding, and evaluating the test basis,we should be able to identify the features and sets of features to be tested. Then we should be able to define and barrier the test conditions for each feature based on analysis of the test basis and considering functional, nonfunctional, and structural characteristics, other business and technical factors, and levels of risk. Finally, we should be able to capture bidirectional traceability between each element of the test base and the associated test conditions. Traceability here means that we need to make sure that we have tested conditions for all the features that we decided to test. Of course, we should do everything we can to reduce the likelihood of omitting necessary test conditions and to define more precise and accurate test conditions. Techniques like Black Box, White Box, and experience-based test techniques,which we will talk about in a later section, can be useful in the process of test analysis. Such test analysis activities not only verify whether the requirements are consistent,adequately expressed, and complete, but also validate whether the requirements accurately capture customer user and other stakeholders' needs. During test design, the test conditions are elaborated into high-level test cases, sets of high-level test cases, and other testware. So test analysis answers the question, what to test? While test design answers the question, how to test? Test design includes the following major activities: designing and preeturizing test cases and sets of tests. The elaboration of test conditions into test cases and sets of test cases during the test design often involves using test techniques, as we will discuss in a later section. Identifying test data required to support conditions and test cases Here we decide what data we should use to test the test conditions and how to combine test conditions so that a small number of test cases can cover as many of the test conditions as possible, designing the test environment and identifying any required infrastructure and tools. And finally, again, we need to capture bidirectional traceability between the test bases, test conditions, test cases, and test procedures. As with test analysis, test design may also result in the identification of similar types of defects in the test basis, which we have said before is a significant potential benefit.

13. Test Implementation and Test Execution

During test implementations, the test, where necessary, is created and or completed, includingsequencing statistical cases into test procedures. So, test design answers the question of how to test. While test implementation answers the question, do we now have everything needed to run the tests? Test implementation includes the following major activities: developing and prioritising the test procedures and potentially creating automated test scripts. Create test suites, form the test procedures and automated testoscopes, if any, and arrange the test suites within a test execution schedule in a way that results in efficient test execution. We will talk more about the management aspect of everything, including testing, in the test management section. Building the Test Environment and sometimes it's hard to build a test environment similar to what the customer has. So in that case, we might also need to build simulators, services, virtualisation, and other infrastructure items like test harnesses. Again, we will talk about this in the next section. After all, we need to verify that everything needed has been set up correctly. And as we have said, we need to prepare and implement tested data and to ensure it's properly loaded in the test environment. Finally, verifying and updating bidirectional traceability between test bases. test conditions, test cases, test procedures, and test suites The service says that test design and test implementation tasks are often combined. Actually, I would add the same idea about NSA testing. This is a critical point. Actually, in simple words, it means that in real life we don't have strict borders between test analysis, test design, and test implementation. Many times, you would be doing all three of them at the same time. I will explain more. So far, we have said we create testconditions during test analysis, we create testcases during test design, and we create or implement test procedures during test implementation. If you created the 20-range test condition during your test analysis and thought that ten would be a good data to use as an input for the test condition, would you say no, I'm in the test analysis right now, and they shouldn't create test cases? Of course not. You simply create what you can while you are doing the analysis, design, or implementation. So really, you use all the information that you have at the moment and you don't really think if you are in test analysis, test design, or test implementation. So, for the exam, yes, we say we create conditions in test analysis and those conditions grow into test cases in test design. And we took the steps to create the test procedures in test implementation. For example, when we ask when do we create test data, we know that data should be created along with test cases. Test cases cannot be test cases without data. However, if we decide that we need a data file to use in our test cases, Then we design the test data in the test design stage, but we actually create the file that contains such data in the testimony design stage. Test Execution During test execution, test suites are run in accordance with the test execution schedule. As tests are run, the outcome needs to be logged and compared to the expected results. And whenever there is a discrepancy between the expected and actual results, a bug report should be raised to trigger an investigation. Test incidents will be discussed in the Test Management section. The following major activities are included in test execution: keeping a log of testing activities, including the outcome, passing and failing the versions of software, data, and tools, and recording the IDs and versions of the test items, test objects, test tools, and test wheels used in the tests. also run test cases in the determined order manually or using test automation tools. comparing actual to expected results analysing anomalies to determine their likely causes Anomalies are when there's a difference between actual and expected results. As we have said before, not every variance between actual and expected results is a bug. Yes, some anomalies or failures may occur due to facts in the code, but false bosses may also occur. I have mentioned false bosses before, remember? Report defects based on the failures observed with as much information as possible and communicate them to the developer to try and fix them. After fixing the bug, we need to repeat the activities to confirm that the bug is actually fixed, which is called confirmation testing. Also, we must ensure that the new fix did not cause any unintended consequences. introduce new bugs in areas that were already working, which is called regression testing. Verifying and updating bidirectional processing, that is, between the test conditions, testcases, testing the procedures, and testing

14. Test Completion

Test completion activities occur at project milestones, such as when a software system is released, a test project is completed or canceled, a milestone has been achieved,an agile project iteration is finished as part of a retrospective meeting at this level, or a maintenance release has been completed. Test completion activities collect data from completed activities to consolidate experience, test results, and any other relevant information. Test completion activities concentrate on making sure that everything is finalized, synchronized, and documented. Reboots rated defects are closed and those defects deferred for another phase are clearly seen to be as such. The first completion includes the following major activities: The documentation is in order; the requirement document corresponds to the design document, which corresponds to the delivered software. Checking whether all defects on your boards are closed out any change requests or product backlog items for any defects that remain unresolved at the end of the test exclusion. Creating a test summary enabled us to communicate with stakeholders while also finalising and archiving the test environment, test data, test infrastructure, and other testware for future viewing. Make sure that we delete any confidential data before handing over the testware to the maintenance teams,other project teams, and all other stakeholders who could benefit from its use. As previously stated, while the main activities in the test process are sequential, they can be thought of as iterative rather than sequential. As an aerial activity, it may need to be revisited according to the circumstances. According to the result of the test report, we might need to reblan the whole testing activity to add more time to the testing activity. A defect found may force us to revisit the analysis of the design stage to create test cases that are more detailed. If we discover a defect, it means that a piece of the requirements is missing, which may necessitate a revisit, planning, and control to allocate time and resources for the newly added functionality. Moreover, we sometimes need to do two or more of the main activities in parallel. Time pressure can mean that we begin testing before all tests have been designed.

15. Test Work Products

Test worker products are created as part of the test process; they are whatever we may need to create during the test process. I was thinking of managing this video with the previous video explaining the testing process group activities, but I said let's keep it this way so you can compare the different worker products easily at each stage of the testing process. Just as there is significant variation in the way organisations implement the testing process, there is also significant variation in the types of worker products created during that process, in the ways those work products are organised and managed, and in the names or titles used for those work products. What we are presenting here are the test workproducts of a very formal test process where we create all sorts of test worker products, which is not always the case for the exam. Of course, we need to know which worker products are created when this syllabus adheres to the testingprocess outlined above, and the work of products described in this service and in the ISTB Grocery ISOStandard ISO IEC Itwille 29119 3 may also serve as a guideline for test worker borders. So just to remember, ISO Standard 29119 is talking about software testing concepts, ISO Standard 29119 Two is talking about software testing processes, and ISO Standard 29119 Three is talking about test work products. So far, so good. Let's now look at the test worker product for every stage in the testing process. Test the Blending: Products tested for blending workerproducts typically include one or more test plans. We will talk about the test plan in the future section, so let's save it for now. Test Monitoring and Control of Worker Products Testmonitoring and control walker products typically include various types of test reboots, including testprogress reports reduced on an ongoing and/or regular basis, and test summary reports reduced at various completion milestones. So just know the difference. Test progress reports are reduced on an ongoing and on a regular basis, while test summary reports are reduced at various milestones. All test reports should provide the audience with relevant details about the test progress as of the report's date, including summarising statistical results once those become available. Test mounting and control worker products should also address project management concerns such as test completion,resource allocation and usage, and effort. We will talk more about the products created during the test monitoring and control phases in the test management section. Worker in Test Analysis Test analysis worker products includedocuments that contain defined and barrier to thetest conditions, each of which is ideally bidirectionallytraceable to the specific element or elements ofthe test bases it covers. There could be hundreds or thousands of test conditions, so we need to utilise them, but the most critical ones first, so we can provide the highest ranking test conditions with more care, time, and effort. Test-Design Worker Products Test design results in individual test cases and sets of test cases that exercise the test conditions defined in test analysis. As we have said, it's often a good practise to design logical test cases, which are also called high-level tests, without concrete values for input data and expected results. Such high-level test cases are reusable across multiple test cycles with different concrete data while still adequately determining the scope of the test case. Again, there could be hundreds or thousands of test cases, so we need to prioritise them both the most critical test cases first so we can provide the highest ranking test cases with extra attention. Ideally, each test case is bidirectionally traceable to the test conditions it covers. Remember that each test can trace back to one or more test conditions, and each test condition can trace forward to one or more test cases. Besides designing test cases, test design also results in the design and or identification of necessary test data, the design of the test environment, and the identification of infrastructure and tools. Though the extent to which these results are documented varies significantly in test design, we can find the need to go back and refine the test conditions that we have defined in test analysis if needed. Product Testing and Implementation As you may have expected already, test implementation workproducts include test procedures and the sequencing of those test procedures. Test Suites also have a test execution schedule which contains the steps to execute the test procedures that are run sequentially at a scheduled time or when they are triggered by a build completion. Again, we will talk more about the test execution schedule in the test management section. Remember that the main objective of testimplementation is to make sure that everything is ready for test execution. Again, there could be hundreds of thousands of test procedures, so we need to perioutilize them,but the most critical test procedures first, so we can provide the highest ranking test procedures. In some cases,test implementation involves creating workable that's used or used by tools such as service, virtualisation, and automated test scripts. This implementation may also result in the creation and verification of this data and the test environment. The completeness of the documentation of the data and or environment verification results may vary significantly. The list data serves to assign concrete values to the inputs and expected results of test cases. Such concrete values, together with explicit directions about the use of the concrete values, turn high-level test cases or logical test cases into executable low-level test cases or concrete test cases. The same high-level test case may use different test data when executed on different releases of the festival. Ideally, once test implementation is complete, the achievement of coverage criteria established in the test plan can be demonstrated via bidirectional traceability between test procedures and the specific elements of the test base through the test cases and test conditions. Test conditions defined in test analysis may be further refined in test implementation. Test Execution work products include documentation of the status of individual test cases or test procedures; for example, ready to run, pass, fail, blocked,deliberately skipped, and so on. And we also have defect reports, which we'll talk about in a different section of the documentation about which items, test objects, or objects, were involved in the testing. Ideally, once test execution is complete, the status of each element of the testbase can be determined and reported via bidirectional traceability with associated test procedures. For example, we can say which requirements have passed blend tests, which requirements have failed tests and/or have defects associated with them, and which requirements have blend tests still waiting to be run. This enables verification that the coverage criteria have been met and enables the reporting of testresults in terms that are understandable to stakeholders. Test Completion Work broader test completion workouts include test summary reports, action items for future projects or iterations, and so on. For example, following an Agile project with respective change requests, product backlogs, and finalised testware.

ExamSnap's iSQI CTFL_001 Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, iSQI CTFL_001 Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.