We're all about testing - how to write better tests, and how to make your code easier to test. We welcome talks on a variety of technologies and code languages.
This Wednesday November 13th at TestableLA, join us for talk by Jason Williscroft: Testing the Untestable. You don't want to miss it: https://t.co/DzhwWWR5C2
Are you interested in testing React components or app performance over various network conditions? Then join us at @carbonfive in Santa Monica on Wed August 14 for this month's installment of TestableLA featuring @WowItsWillWow and @dc_palter!
RSVP here: https://t.co/Uzw3TXK10F
Are you a software #tester who hasn't ever coded before but really wants to learn #Java? @TechGirl1908 has created for @TestAutomationU a free course just for you, sprinkled with Angie Jones' fun and energy, with cute musical breaks.
#qa#sqa
https://t.co/h08xbdahHX
Testing, logging, and observability are not afterthoughts that you address when all the features you want have been written, they are part and parcel of engineering work.
Andy Knight (@AutomationPanda) will join us again in July to talk "Writing good Gherkin"
Join us July 23, 2019 at 1pm EDT.
https://t.co/0CCuLTZCdN #BDD#Gherkin#Automation
"Creating specifications that express intended behavior of a feature and that are understood and agreed upon by the whole team, results in a set of acceptance tests that are a great starting point for both testing and test automation."
https://t.co/9bID9zEstF by Bas Dijkstra
Collaborate with your team to evaluate each step in your pipeline:
What purpose does it serve?
What is it dependent upon?
What triggers it?
How long does it take to get feedback?
Then you can identify pain points and plan to alleviate them!
https://t.co/GvyA4LVcIs by @lisacrispin
"A large focus of my work as a tester was falsifying the idea that the product works. I wanted to find ways that the software, in all its context, might not help our customers do what they need to do."
https://t.co/XmcMhWyi5e by @JustinRohrman
You don't have to be an expert on a topic to write a blog post. The best "101" introductory blog posts are often the ones where you're walking through how YOU learned something new - both the wins and the struggles.
Manual testing provides the most value when you:
1. Understand requirements
2. Time-box exploratory testing
3. Prioritize test cases
4. Test before deploying
5. Report defects correctly
6. Implement traceability
7. Perform root-cause analysis
https://t.co/rOI7735J8B by @ailuj876
Want to attend one of our TestBashes or get a pro membership but don't have the funding? We've got you covered with the scholarship fund! Read how to apply & previous recipients experiences. We want to support you https://t.co/iaIJdmPFrv #SoftwareTesting#Scholarship
By Monday, you'll be tired of BBQ, cookouts, and fireworks, right? Come join us at this #MeetUp for pizza, #testing, #automation,...and cast iron? We still have seats available!
https://t.co/jPBcCSAzbz
We are hiring for exploratory and UI automation testers on my team, which works in Non-Profit and Education clouds at Salesforce. Accessibility experience a plus. Fully Remote, US only. Message me if you have questions!
https://t.co/p82YcLAx03
Just announced! Our #meetup on July 10th hosted by @carbonfive in Santa Monica will feature our friends Inga and @JohnTellsAll speaking about designing and testing for security. Join us!
https://t.co/IZewFLL40A
We're very excited to have @alex_schl doing a #dojoMasterclass soon on Exploratory Testing - specifically microheuristics - who knew there was a reason we made the decisions we do while Exploratory Testing! Save your space https://t.co/g8g0LHSrzT #SoftwareTesting#Testing
Had a great time talking at the Testable LA Meetup last night. I was impressed by all the @Cypress_io questions. In my next talk I’ll dive deeper into Cypress API and functionality. Thanks to @carbonfive for hosting the event. #javascript#LosAngeles#FrontEnd#dev