Пікірлер

• 
  @pudercukursАй бұрын

  Thank you

• 
  @emattaАй бұрын

  We should not fear AI but look forward to it removing the cruft so we can properly investigate issues and implement solutions.

• 
  @rothbardfreedom7 ай бұрын

  "Soft Skills: The Software Developer's Life Manual" John Sonmez

• 
  @MinistryofTesting7 ай бұрын

  Thanks for the recommendation :)

• 
  @danieljuhlkristensen125911 ай бұрын

  You reference a book in the begining, what book is it you're recommending here?

• 
  @MinistryofTesting11 ай бұрын

  Building Successful Communities of Practice: Discover How Connecting People Makes Better Organisations by Emily Webber. www.amazon.co.uk/Building-Successful-Communities-Practice-Organisations-ebook/dp/B01BYH07P0/ref=sr_1_1

• 
  @Horshack187 Жыл бұрын

  In terms of easy it is to test a system I’d add if there are hooks built into the platform for testing. Additionally, is the system being built TDD? Two things you want to see in a platform for testing.

• 
  @MinistryofTesting Жыл бұрын

  Excellent examples. I personally find if good TDD is being practised then hooks for testing emerge naturally. - Mark

• 
  @rothbardfreedom Жыл бұрын

  Sprints are mini-waterfall.

• 
  @MinistryofTesting Жыл бұрын

  What makes you say that? I know I have faced my fair share of Wagile contexts, but I've also been in teams where we took each story at a time in a collaborative fashion and reacted to end user changes as we released. - Mark

• 
  @mirzasisic Жыл бұрын

  Hey I actually applied Pirate Tester's advice: in my second company I spoke at the internal meetup, which was less scary since the audience was smaller and I knew everyone in the audience. Later when I did that same talk at a bigger public meetup and had already re-hersed it in a "product-like" environment and went really smoothly! It's a very good peace of advice!!

• 
  @MinistryofTesting Жыл бұрын

  Great story Mirza. Personally it's something I've done for a long time when preparing my own talks. I share 'draft' versions that are shorter and a bit rougher around the edges. It helps me get comfortable with material and solicit useful feedback on what to add and what to improve. - Mark

• 
  @PaulGrossmanTheDarkArtsWizard Жыл бұрын

  Mark manual test Jira tickets as “Automatable” and later “Automated” or “not-Automatable” Add the manual test Jira Ticket link(s) to the Allure results. Strive for 80% coverage before moving to next subcategory.

• 
  @zshn Жыл бұрын

  If your org's development strategy is API first, then yes. If not, then prioritize UI performance testing. Testing should cater to customers first. In an API-first strategy, the customers are developers, therefore API testing should be prioritized. In a non-API-first strategy, the customers are users who interact with your org's product using a UI, therefore UI testing should be prioritized.

• 
  @MinistryofTesting Жыл бұрын

  Context is always key in these types of discussions which you're demonstrating in your comment @zshn. It could be both could be prioritised and carried out at the same time, but we need the right skills, experience and support. That all has a huge impact on our decisions. - Mark

• 
  @mirzasisic Жыл бұрын

  I really like that MoT has been active on all fronts lately!

• 
  @Paitent12345 Жыл бұрын

  You are actually talking about test plans. Test strategy should be pretty general and does not have to be specific. It is a general approach from which specific test plans are derived. Thus, test strategy could and IMHO should be very brief and general. If you need anything specific, than one should ask about test plans, not strategy.

• 
  @MinistryofTesting Жыл бұрын

  It's a tricky thing Strategies and Plans. I would definitely subscribe to the idea of my strategy is my vision, whereas my plan are my concrete steps to take and mitigation if the plan goes sideways - Mark

• 
  Жыл бұрын

  great response! Visual test strategy and people working together 👏 "the better the people are the briefer the documentation can be"

• 
  @nyasham1 Жыл бұрын

  Solid tools there. Thank you for sharing. Just to add another I really like is assertion libraries like fluentassertions, assertpy and assertj. They provide interfaces for more easy and readable validations in your test code

• 
  @MinistryofTesting Жыл бұрын

  Great tip! You should totally add them to our Tool directory if they're aren't already there: www.ministryoftesting.com/directories/tools - Mark

• 
  @ResterTest Жыл бұрын

  @MOT and @Vernon how can one pe part of these sessions?

• 
  @richardbradshaw6217 Жыл бұрын

  I'm about to open a call for contribution for AMA guests in the coming week. Keep an eye on all things MoT.

• 
  @ResterTest Жыл бұрын

  @@richardbradshaw6217 - Will do

• 
  @photos8690 Жыл бұрын

  Here is a updated version with beats and lyrics: kzread.info/dash/bejne/mYFt0JlslrCpqLQ.html

• 
  @Patrick002 Жыл бұрын

  Insightful and very educational

• 
  @MinistryofTesting Жыл бұрын

  Thanks Patrick, glad you liked it. Keep your eyes peeled for more accessibility content coming soon.

• 
  @oleggrudko8137 Жыл бұрын

  Cool explanation. While watching this video I applied another concept from the levels of knowledge described by Neil DeGrasse Tyson. There are things we know that we know - those can be covered by scripted tests, they are mainly included into accepted tests There are things we know that we don't know. Those are minority of acceptance tests, mainly exploratory tests There are things we don't know that we don't know. Those are defects slipped to production ... And they should be covered by getting feedback from customer support to incorporate them into our knowledge body

• 
  @MinistryofTesting Жыл бұрын

  Really insightful Oleg thank you!

• 
  @TheLudema Жыл бұрын

  Interesting, thanks 🙏🏻

• 
  @MinistryofTesting Жыл бұрын

  Glad you liked it!

• 
  @m3tomlins Жыл бұрын

  This was in 2017. TestBash San Francisco was 2018

• 
  @abellagonzalo2 жыл бұрын

  Loved the podcast! Where can I find all the links and videos you are talking about?

• 
  @zephatay1813 жыл бұрын

  Thanks. It helps me a lot.

• 
  @MikhailLaptev4 жыл бұрын

  Great explanation! I'm happy to see that I've built our framework in the right way :-)

• 
  @vitaly71964 жыл бұрын

  Good job!

• 
  @vincentdirks1894 жыл бұрын

  thanks for recording this Mark. It was great start for me to see REST Assured and creating a new java automation framework in action.

• 
  @dprouty4 жыл бұрын

  where can we find the lyrics?

• 
  @cipriansmith33734 жыл бұрын

  experimentation learning free style exploration Studying and modelling conjecture observation test code development task prioritization testing out competitors preparing simulations formalized reporting to comply with regulations gathering assessing and applying information deliberation judgment designing visualizations setting up the lab to try complex configurations working out the problems in a puzzling situation finding ambiguity in a product specification trying to look beyond the predicted expectation well that’s cos testing is all about investigation questioning and learning playful product interaction trying to keep my focus while I’m managing distraction sense making myth breaking breaking decisions make no faking stressing out the product to discover where its breaking interrupted disrupted because the products full of bugs the fellow who developed it must have been on drugs refining test approaches through deliberate practice how could hackers hack this don’t give the access wrestling with problems in the setup of environments interviewing users to discover their requirements so I shall socialize to provoke collaboration other folks can help me with my testing preparation talking with the managers to learn what they require testing for charisma that’s what customers desire working with the marketers to show the apps Power Point to all the features try to finish in an hour selecting configuring and then applying tools remembering critical thinking confirmation is for fools refactoring in every step keeping things maintainable let’s get over overtime and make the pace sustainable building coverage models analysing risk and eliminating waste trying to keep the pace brisk pattern recognition distributed cognition helping shy colleagues get over inhibition but I want to say this While I'm in a rap rhythm that a checks a part of testing encoded in algorithm testing’s much more than automated checks and test cases human variation puts a product through its paces talk of manual testing will keep out craft stuck but testers keep referring to it I say what the use the tools powerfully that’s what I’m suggesting but don’t try to tell me you can automate the testing

• 
  @ptvptv38275 жыл бұрын

  This would be great I've just started a job and they are putting me on the mobile team

• 
  @StefaniaIoanaChiorean5 жыл бұрын

  Hey - any links here for this? I am not finding anything on MoT

• 
  @MinistryofTesting5 жыл бұрын

  Hi Stefania, it's not live yet - once it is I'll update the links and we'll share it all over on our social and news updates. Thanks - Áine

• 
  @rayoei96516 жыл бұрын

  I see a new career ;-)

• 
  @shwampy7 жыл бұрын

  Enjoyable, thoughtful talk.

• 
  @m3tomlins7 жыл бұрын

  See you again in 2017! November 9-10th!