@ThePragmaticEngineer
Software Engineer
Hi, I'm Rafael, but you can call me Rafa! 馃槃 I'm a software engineer passionate about everything that involves technology, with more than 5 years of experience in the market. Throughout my career, I worked in banking institutions, developing innovative solutions and contributing to the digital transformation of the financial sector.
With a strong interest in software architecture and testing, I am constantly looking to specialize and improve my skills in this area.
Here, you will find tips, tutorials and discussions on the most varied topics related to architecture, good practices and software testing, always with the aim of sharing knowledge and learning from other developers. I value the exchange of experiences and I am always willing to listen and learn from my professional colleagues.
Feel free to get in contact, leave your comments and share your own experiences and knowledge. Together, we can build a stronger, more collaborative community in the software development world.
Nothing here yet.
Exactly Anthony Fung , it already falls in frontend cases in specific situations where it was necessary to perform two actions. In most cases this was not necessary. When I began to apply a critical eye more frequently to unit tests, I began to observe that the more actions in a single test method, the more easily it broke.
Anthony Fung Nice, I think it's important to have this view you commented, in the last year I have adopted a more simplistic testing strategy, look at the requirement, understand the expected behaviors and just check what really matters in the assert. I also look for invalid scenarios, unusual inputs that I wouldn't normally think of if I just did the happy path of unit testing. Obviously this is not always easy to apply, especially in complex systems. I am writing about this as well. What strategy do you usually put into practice for your test cases?