Слайды и текст доклада
Pic.2
Introduction of Quality Assurance
Pic.3
Testing in a nutshell Competencies: - Guarantee quality of a product - Finding defects (bugs) - Preventing bugs - Work with docs
Pic.4
Couple of words about documentation 1. Test cases; 2. Test plan; 3. Check list; 4. Test suite; 5. Bug reports.
Pic.5
Test plan Test plan – main document for application testing. It describes testing strategy and testing approaches. It contains following: •Title, author, version control, history of changes •Table of …
Pic.6
Some facts about test cases • Test cases can be based on requirements (specifications, communication with customer, mails) or existent functionality • Used for requirements coverage, providing more …
Pic.7
New test case. What to start with? Learn requirements and pick out all possible cases including negative cases Check the genuineness of the test case Test case should describe an atomic independent …
Pic.8
New test case. Let’s focus on attributes Unique ID. Author Revision history Priority (critical, major, minor, trivial) Description Preconditions, steps and expected result Post conditions Comments, …
Pic.9
New test case. Let’s focus on attributes
Pic.10
Test suite. Briefly Test suite – batch of test cases, which check certain functionality. For example: User registration Sending messages Removing account
Pic.11
Test suite. Example
Pic.12
Check-list. Main purposes Check-list – list of attributes, applications, characteristics and checks themselves, need for testing. Mainly used for internal needs. Also: Allows tester not to forget to …
Pic.13
Check-list as it is
Pic.14
One more thing. Bugs. Bug is nothing else but program flaw, in other words – defect in software. It can be found while testing software application or product, and usually means difference between …
Pic.16
Bug reports Each bug should be conveyed to the developer. Thus, bug should be reported in a appropriate way. That’s why we need documents called Bug Reports. They should contain following: Defect ID …
Pic.18
Bug’s lifecycle 1. Finding defect. Status – New 2. Dev team with Project Manager decides whether defect is valid. If not – status Rejected 3. If the defect is not rejected then the next step is to …
Скачать презентацию
Если вам понравился сайт и размещенные на нем материалы, пожалуйста, не забывайте поделиться этой страничкой в социальных сетях и с друзьями! Спасибо!