How do you use testing techniques and frameworks?

Personally, psuedocode is always the way to go for me when I am writing code alone. TDD and BDD get in the way. However if you start with enough words written in your education before you are completely prepared for this. This also means that your test writing ability goes unused.

Apart from the stated types of testing, there is functional testing which is aimed at verifying that the Software functions according to its specifications. It specifically checks if the Software meets the functional requirements. Performance testing evaluates the system's speed, responsiveness, scalability, and stability under different conditions such as lower bandwidth networks. Load testing, Stress testing, Alpha testing, and Beta testing are among other various forms of Software Testing.

...and thank you to the websites offering classes and examples for these testing environments. There is no way to teach these with undocumented test platforms and the testing for websites and connectivity is so crucial for web projects and microservices.

Testing frameworks go beyond what is already stated here. Testing frameworks involve other aspects such as Contract Testing Framework which enables interactions between MicroServices and API consumers and providers. They ensure that both parties adhere to predefined contracts regarding data formats and communication protocols. Visual testing frameworks that capture screenshots and renderings and compare them to baseline images to detect visual regressions such as Applitools and Percy. Continous Testing frameworks such as Jenkins and Travis CI, integrate with Continous integration and Continous delivery pipelines to automatically trigger tests whenever code changes are pushed among others.

We practice Test-driven Development to ship our enterprise-grade React app. Here’s the workflow: 1. Jump on a pair programming session with a test engineer to write acceptance test replicating a user journey (e.g., create a todo item). 2. A mob programming session with engineers to implement software behavior that completes the user journey we wrote a test for. 3. When the test passes (green), we refactor the underlying code to make it easy to change. 4. Repeat the workflow from 1) until all user journeys are asserted and the feature is implemented. TDD helps to build a safety net that will instantly tell whether we broke some existing software behavior when developing new features. Plus, it’s super fun because of a teamwork.

BDD is a user story and then code from that user story. This isn't much a of a change for most Agile programmers. With Spring Boot I have seen a slow implementation of TDD, but with so many more resources online this is changing.

One thing I would like to spend more time on if I ever have the chance to is to go over the old math for requests with a tool like JMeter. I have never used it, but without a cloud expert who would know this is probably a tool for a demo you need to sell your idea, readiness or whatever else for your next meeting.

I can't say it any clearer than this. A company level project with the code and testing is a collaborative effort and forget any small issues if you don't have a collaborative approach.