Last update 24 Oct 2016
- Главная
- Разное
- Дизайн
- Бизнес и предпринимательство
- Аналитика
- Образование
- Развлечения
- Красота и здоровье
- Финансы
- Государство
- Путешествия
- Спорт
- Недвижимость
- Армия
- Графика
- Культурология
- Еда и кулинария
- Лингвистика
- Английский язык
- Астрономия
- Алгебра
- Биология
- География
- Детские презентации
- Информатика
- История
- Литература
- Маркетинг
- Математика
- Медицина
- Менеджмент
- Музыка
- МХК
- Немецкий язык
- ОБЖ
- Обществознание
- Окружающий мир
- Педагогика
- Русский язык
- Технология
- Физика
- Философия
- Химия
- Шаблоны, картинки для презентаций
- Экология
- Экономика
- Юриспруденция
QA approach in MeriVal Description of new approach from Luxoft Krakow ODC презентация
Содержание
- 1. QA approach in MeriVal Description of new approach from Luxoft Krakow ODC
- 2. Agenda “As Is” QA processes overview and
- 3. Purpose of the meeting (STATEMENT) Current approach
- 4. Systematic approach Same approach for all Quality
- 5. PP28 (IFRS9) EXAMPLE Different approach Challenging
- 6. Action steps Current challenge – PP28 development
- 7. Expected results The exact results we would
- 8. THANK YOU
Agenda “As Is” QA processes overview and ways to improve. Proposed best QA practices. Detailed description of artefacts and “To Be” state The highlights of our presentation
Слайд 1QA approach in MeriVal Description of new approach from Luxoft Krakow ODC
Слайд 2Agenda
“As Is” QA processes overview and ways to improve.
Proposed best
QA practices.
Detailed description of artefacts and “To Be” state
Detailed description of artefacts and “To Be” state
The highlights of our presentation
Слайд 3Purpose of the meeting (STATEMENT)
Current approach
Functional changes – 48% during UAT
Spending
time on fixing bugs VS spending time on proper test analysis
Слайд 4Systematic approach
Same approach for all Quality Assurance tasks
Current experience:
No QA
artifacts available
Each team has it’s own approach to the test strategy (lack of standardization causes lack of guarantees of coverage)
Gaps in test coverage with current approach (PP28 – IFRS9)
Modules with incomplete E2E coverage (quaterly basis, separate functions etc.)
Each team has it’s own approach to the test strategy (lack of standardization causes lack of guarantees of coverage)
Gaps in test coverage with current approach (PP28 – IFRS9)
Modules with incomplete E2E coverage (quaterly basis, separate functions etc.)
Слайд 5PP28 (IFRS9) EXAMPLE
Different approach
Challenging the current approach with best QA
practices
Test design techniques
Flow chart
Flow prioritization
Working directly with the code (fitnesse debugging)
Test design techniques
Flow chart
Flow prioritization
Working directly with the code (fitnesse debugging)
Слайд 6Action steps
Current challenge – PP28 development
Update and finalize the FlowChart for
current part
Create FlowChart for the rest of the module
Create traceability matrix for main parts (IFRS7&IFRS9)
Find the uncovered flows and create test cases
Results of the investigation would be put into document
Follow-up session (5-6 weeks)
Create FlowChart for the rest of the module
Create traceability matrix for main parts (IFRS7&IFRS9)
Find the uncovered flows and create test cases
Results of the investigation would be put into document
Follow-up session (5-6 weeks)
Слайд 7Expected results
The exact results we would like to reach in new
approach
Measure test coverage
Significally reduce number of UAT defects in
Share documents with results of investigation with effectiveness of new approach
