Hi there!
I just started a new blog. And I dedicate it to situations when testing gets nasty.
What does it mean? I have a good example. Imagine that developers tell you: “Hey, mate, this new project will be awesome! We have huge plans! New services, new technologies, and we need a high quality product!”. And you think: “Aaah, man, how am I supposed to test all this stuff?”. Yeah, things are getting tough… You have a lot of question and it will take some time to find answers. But in the end they will tell you: “Dude, how did you find all these nasty bugs?”
Few questions to start with for practicing:
Why am I reading this?
Most likely you found this website in Google or some other search engine. And it seems there is something here you are interested in.
Why are you doing this?
I just want to make some notes for myself and probably some people who involved in software testing but not quite sure how to do certian things yet. So, I hope I have some knowledge to share.
What is this all about?
It’s all about software testing and/or quality assurance, tests automation and many technical things related to this.
Can I have more details?
Yes, sure. Some examples:
- Test design
- Test frameworks
- Test automation
- Performance testing
- CI/CD
- Linux
- Docker
- Bash scripting
- Java
- Python (well, may be, can’t guarantee this one)
- API (REST)
- HTTP
- SSL
- Some other nice technologies you may need to use while testing
- My opinion on different things
Why should I trust your opinion?
You should not. It’s always good to have different points of view. Don’t be shy, write what you think, and we can discuss further.