Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
Complexity is a property of software systems with lots of components that interact in lots of ways. Bugs thrive in complexity. Inert bugs in one component may be activated by seemingly unrelated changes in another. Latent bugs may take years to be observed or detected by software testing.
This is a hands-on practical session about agile testing where participants split into groups and learn how to do story mapping and how to write Given-When-Then Behavior-Driven Development (BDD) tests.
This talk aims to introduce property-based testing, why you may want to use it, and real-life use cases for including it in code bases. Property-based testing is an approach to testing that involves specifying statements that should always be true (for example, reversing a list twice will give the original result) rather than relying on specific examples.
In an era where artificial intelligence (AI) writes code, reviews pull requests, and even generates tests, how does the standard Testing Pyramid still hold up? Has it quietly crumbled under more modern demands?
It appears that one consequence of being a tech lead is that team members consider you the default reviewer for all their pull requests (PR). Though the code review process seems straightforward, there are many aspects that need to be considered.
In a lot of software development teams, test automation code is treated much less carefully than production code. It is expected to just work. Mindless copy and paste of setup code from one test case to another is seldom seen as problematic, scripts duplications are widely accepted, and things are named randomly.
To date, web applications have been the focus of digital accessibility tooling. Attention is now pivoting to mobile apps that are usually tested with Appium. So how do we test mobile apps for accessibility? Many organizations test their apps with assistive technologies.