Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Teamwork From individual effort to holistic con...

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

Teamwork From individual effort to holistic contribution

Teamwork From individual effort to holistic contribution presented by Mesut Durukal in Japan Test Community January onsite meet-up, Tokyo.

Avatar for Mesut Durukal

Mesut Durukal

January 22, 2024

Other Decks in Technology

Transcript

  1. • Teamwork vs Individual work • Forming a team •

    Characteristics of a team • The story of my team
  2. In the interview, you are asked if you want to

    work individually or as a team member. In your first day at work, you are asked to meet with your team.
  3. How is it different? Advantages • flexibility and independence •

    fast reactions or updates: easy decision making • ability to focus on what you want or need to accomplish a task • complete control of the direction and process of how you work • receive all the credit, praise and benefit for achievements • more diverse thoughts and different perspectives • more support and collaboration • build workplace relationships and network • feedback and review
  4. How is it different? Challenges • maintain motivation • lack

    of stimulation in terms of conversation, meetings or group discussion • direct responsibility • less oversight and guidance • several meetings • manage differences or even conflicts • need to stick to defined schedules • need to succeed consensus and convince everyone
  5. Characteristics of effective and great teamwork • Open communication •

    Support & Respect • Problem solving • Self growth • Diversity • Engagement • Trust
  6. Initially • Define a test suite • Automate • Report

    results • Kyla • Leo • Susan • Each person designs tests • Each person creates their spc files & report results
  7. Then • Define a test suite • Automate • Report

    results Whole team • Brainstorming for designing cases • Exploratory testing session • Figure out common features • Develop a framework • Create spec files using common features
  8. cy.get(button + ':visible') .click() .invoke('text') .as('labelOnButton' ); cy.wait(2000); cy.get('@labelOnButton' )

    .then((actualLabel )=> { expect(actualLabel ) .to .equal('25 k’)}) Kayla Leo Susan cy.get(button + ':visible') .click() .should('contain', '25 k’); cy.get(button) .should('be.visible') .click() .should('have.text', '25 k’); Rob cy.get(button + ':visible') .click() .then((button)=>{ expect(button .text()) .to .equal('25k’);}) myFramework.checkText(filterButton, '25 k')
  9. • Developing standards. • Avoid any antipatterns. • Remove duplication.

    • Provide solutions to common problems. • Provide an opportunity for monitoring • Dashboards, queries, filters, charts Achievements
  10. • Being a team is not easy ◦ Common decisions

    ◦ Consensus on the roadmap • Challenges ◦ Deal with differences ◦ Deal with conflicts • ROI in the long term • Finding support is important • Boosts efficiency by eliminating duplication • Ok to fail but know that you are not doing the best..