Please enable JavaScript.
Coggle requires JavaScript to display documents.
QE Journey - Coggle Diagram
QE Journey
Development
TDD
Strengths
exists in some areas
Tools (Nunit etc..)
Weakness
the coverage less
Bridge
improve the coverage but how?
Code review
Strengths
githug code review request. min 1 person does the review
auto review on some sensitive code
Weakness
nothing stopping the commit if they break the build
Bridge
Train the team
Clean code
Strengths
guidlines in confluence
sort of tech discussion with India team
Weakness
Legacy code
No defined tools
some new code is written in Swedish
Bridge
not to write swedish code
train the team
Reusable components
Strengths
security related
attributes
localization
developer news in Confluence
Weakness
code is large,not every developer know everything
Bridge
sharing the components/reusable
RCA of customer bugs
Strenghts
support team
critical bugs we do RCA
Weakness
Not sure sweden team's process for customer
Bridge
we need support from Sweden
Requirement
Strengths
Weakness
Bridge
Testing
Improve Windows
Strenghts
manual test
Ranorex
Weakness
automation with ranorex but <10%
only 4 ranorex license for team of 12 testers
Bridge
increase automation :
get more ranorex license
Improve Web
Strengths
manual and automation
Robot is open source
India team write more automation
Weakness
functional coverage is less
Bridge
improve the coverage > 90%
Functional coverage
Strengths
manual testing 90%
Weakness
automation is only <30%
Bridge
improve automation to >90%
Security & Performance
Weakness
we dont have tools
no automation
Strengths
app wise manual test
authorization
can find missing authorization
Bridge
find tools preferably free ones