Please enable JavaScript.
Coggle requires JavaScript to display documents.
Best Practicies - Coggle Diagram
Best Practicies
Test manager
Test environment
Monitoring
Support of the Test environment avaialability
Test environment access for testers
Plan
Preparation for testing
write test cases
collect/create test data
test cases review
workshops for the test case creation with architects
Configuration of the environment
Kick off
communication plan
escalation path
reporting
stakeholders
Test comunication
Share storage oif the test artefacts
Documention guidilines
Team members (daily status calls)
Work progress
Respond to Stakeholders needs
Preparation of testing tools
Testing tools installation
Testing tools guidelines
Guideline for stakeholders
Statuses
Reporting
Agreement on naming convention
Testing tool administrator
Test management tool
Setup guideline for priorities
Test cases repository
Regression tests easy to derive
Preparation of Test Schedule
Defect management
Guideline for defect creation
SPOC for defect management (including communication about defect retest and installation)
Input for defect management board
Identification of impact of defect on testing
Collecting lessons learnt
Share place for LL
Conducting and implementing LL process
Risk management
Preparation of contingency plans
Risk mitigation
Owner of testing related risk
Risk identification
Test Concept
prparation
Recognition of the work result
Tester
Test environment
Ready for use
possibility to configure enviorrment
Daily monitoring of the test environment
OPS team dedicated for solving the test environment issue
Lessons Learnt
Tester have a possibility to enhance the testing process
Tester have a possability to suggests enhancments to software and the process
Customer agent
possability to know customer needs
Cutomer personas
Tester involved from beginning of the Software change process
estimation
Specification analisis
Customer test cases creation
exploratory testing as a tool for learning
Coaching
Test case reviews
Technical skills development
knowledge sharing
Support of the carrier path
Test proccess
Ensuring transparency by description of Test process
Test process well known for all of the stakeholders
RACI
Test procedure START/STOP creteria
Checklists for the testing procedures
Documentation
Test cases
best practicies
Know the requirements
Understanding of the design and implementation.
Know the application
TC should be easily understand without any ambiguity
Test Description
Cover all the positive scenario
Follow Naming Convention
Give some test data for example
Negative testing
Precondtions
Atomization
easy to derive bug from test steps
story behind
Good TC is
Accurate
Economical
Tracable
Repeatable
Reusable
Requirments
best practicies
Language and style
understandable
clear and easy
straight and hard facts
no for generalization
Graphics
screenshots
sketches
Personal features
non personal language
'non technical person'
