STAREAST 2023 - Tester | TechWell

Conference archive

STAREAST 2023 - Tester

Monday, May 1

MB

Getting Started with AI-Driven Automation

New
Monday, May 1, 2023 - 8:30am to 12:00pm

AI has been rapidly changing the way we approach software testing. Traditional test automation is time-consuming to create and breaks down easily in the presence of change. Thankfully, AI is helping testing teams create less procedural, more resilient tests that are able to self-heal in the presence of modern, rapidly changing, highly dynamic production systems. This sounds great, but you may be asking yourself: How do I get started? What additional skills do I need to learn? What tools are available for me to start using, right now? Join Dionny Santiago as he breaks down different AI...

Wednesday, May 3

Big Data Florida
W8

Data Science and System Testing: Lessons Learned from a Four-Part Workshop Series

Wednesday, May 3, 2023 - 1:30pm to 2:30pm

During fall 2022, Big Data Florida ran a series of four workshops on the intersection of data science and system testing. The first was on “Testing Big Data Systems,” which provided the basis for subsequent meetings. The second event was on “Testing Machine Learning (ML) Models,” the third was on “Testing Artificial Intelligence (AI) Applications,” and the fourth was on “Leveraging AI and ML in Testing.” Participants were an interdisciplinary group drawn from data science, testing (hardware, software, and integrated systems), and interested researchers and professionals. This session...

Infotiv
W14

Testing Machine Learning Functionality: The Need for a New Way of Thinking

Wednesday, May 3, 2023 - 2:45pm to 3:45pm

When testing functionality based on machine learning or trained functionality, the focus of your testing changes. The code itself stops being interesting to some degree, and instead the focus needs to be elsewhere. Based on personal experience and research projects, this session will highlight the importance of testing your data, why independent testing is vital, and how some "old school" tools can help when thinking & planning test activities. This session will also demonstrate trained functionality intended for autonomous driving, and will touch more general problems faced when...

Thursday, May 4

Sony Interactive Entertainment
T4

Testing Hard-to-Test Devices Using Docker Containers

Thursday, May 4, 2023 - 9:45am to 10:45am

Back in the day, live testing was the only way to test systems, especially software and hardware, and the advanced methodologies that we have today did not exist. Today, docker containers have made even the most difficult systems very easy to test. In this session, we will take a look at an example of testing a disk monitoring service using software techniques without actually using any disks. The service reports NVMe SSD drives’ state and classifies drives as “good” or “bad” based on the data. Key takeaways from this session include understanding the basics of NVMe and docker, creating a...

Auction Edge
T5

Small QA Team Survival Strategies

Thursday, May 4, 2023 - 9:45am to 10:45am

Are you and your team having trouble managing your workload? Is your Dev to QA ratio completely out of whack? Do you need help convincing management that one or two extra hands would make a difference? Amanda will draw from her experience on teams of various sizes to provide examples of how to organize the QA workload into manageable pieces without losing your sanity. She will also give advice on how to outsource to other non-QA team members that can assist with getting stories to done and avoid potential bottlenecks. We’ll also discuss ways to get developer assistance with unit and...

T8

Comprehensive API Testing Ecosystem

Thursday, May 4, 2023 - 11:15am to 12:15pm

Maintaining API test cases across multiple environments, for different load levels, and types of tests (eg. smoke, functional, regression) traditionally required separate tests be written and maintained. Test maintenance is expensive. If you have three lower environments that tests are run for, then you usually have at least three different tests you are trying to keep in sync. If you have a new API added for a microservice, then you have to modify and validate across all three tests at a minimum. If you are running different load levels for build tests verses load tests, for example, that...