https://www.linkedin.com/in/vladyslav-zagorodnyi/
https://www.facebook.com/vladyslav.zagorodnyi.7/
https://www.facebook.com/groups/qualityassuranceglobal
This video is created to learn basics of manual quality assurance activities or it’s fundamentals. This information will be the most relevant for people who’s no experience in manual quality assurance industry or for junior qa engineers who has limited test experience. In video we talked about: QA Purpose, Testing, QA, Quality Control, Software Development Lifecycle (SDLC), Software Testing Lifecycle (STLC), Quality and it’s attributes, Test Types (Black Box, White Box), Test Design Techniques (Equivalence classes, Boundary Values, Decision Table, Pairwise, State Transition, Domain Analysis, Use Case), Test Levels (Unit, Integration, System Acceptance), Test Documentation (Test Plan. Test Case, Test Set / Suite , Checklist, Bug Report) It’s the most relevant scope of information that person need to know to apply and get your junior manual QA engineer position. I think that you find out Information Technologies like sky - rocketing industry that you gonna join. I'm happy to be your guide here, welcome on board. At the first slide we identify the purpose and reason why QA is needed. Quality assurance engineers are needed to take control over software quality, identify issues, escalate and verify them by the process of creation and running test cases to verify actual result meet requirements and user expectations.
What is testing? It is a specific research to provide information about software quality. What is Quality Control? It is process by which product quality is compared with the applicable standards and the action taken when non conformance is detected. What is Quality Assurance? Set of activities which confirm that products and service fit to specified requirements and correspond user expectations. SDLC diagram is best evidence that allow to understand development flow. Each product pass the next stages: Requirement Analysis - here we establish the problem, propose idea, make market research. On Design stage we create requirements, mockups , strategies, indicate development timeframes and prepare budgets. During Implementation stage - we hire team and start to develop. On Testing stage - test activities are performed, we establish the scope of tests, test strategy, applicable test techniques to use, identify bugs and verify their fix. Evolutions stage allow us to enhance product , deliver new features and make next steps.
Quality - it is degree to which, system meets requirements and customer expectations. The product quality model defined in ISO and consist of 8 items: Functional Suitability, Performance Efficiency, Compatibility, Usability, Reliability, Security, Maintainability, Portability. Scope of applicable to test quality attributes is determined subjectively by each product you will work on and each task you will be assigned to.
Software Testing Lifecycle it's is specific QA flow that engineer should follow when he get's new task assigned on. STLC Consist of several stages: Test Planning - QA should analyze requirements, establish test strategy and approve it. Test Design - process of creation test documentation: Test Plan, Test Sets, Test Cases/Checklists. Test Execution - process of test cases running. Defect Reporting - organize all differences between actual and expected results into Bug Reports. Defect Verification - Perform retest of all found issues. Software has it's own specific requirements (SRS) , that consist of 3 layers: Business Requirements - explain the business model, why do we create this application, how we will sale it; User Requirements - describe scope of functionality that we will deliver to customers, create sitemap of user needs, System Requirements - indicate what technical prerequisites are needed for our system (application) to run. Manual QA will often interact with User Stories (especially junior).
Goal of video is explanation of Black Box Test Design Techniques. Equivalence class - it is a set of values (tests), full execution of which is superfluous and does not lead to the discovery of new defects, cause same output. Boundary values - points where system’s output change, depend on equivalence classes. Decision Table - tabular representation of inputs, rules, cases, test conditions. Pairwise (due to IBM research interaction of 2 params cause 97% of software issues) - each test value of each of the checked parameters is at least once combined with each tested values of all other checked parameters. State Transition - this test technique is able provide a pictorial presentation of system logic and state changes that allow tester to understand the system behaviour and create efficient test design.Domain Analysis - analyze range of applicable values, identify sub-ranges inside. Use Case - scenario of software usage, where the main attention is paid to interaction between actor and system.
розгорнути опис
згорнути опис
