How many tests should I have

Probably most of us seen or came to a project where there was no tests or there was very few of them. On the other hand there is another big fraction of software (quality) engineers struggling with test suites that last for hours. In both situations the main question we should ask is “how many tests should we really have?”.

This is not that easy question to answer. First of all we need to realize why exactly do we need automated tests… Basically there are three main reason to automate testing effort:

Continue reading “How many tests should I have”

Continuous Integration #1: How to speed up gradle builds

It’s absolutely great that continuous integration become a standard lately but the success of this approach is determined by feedback loop time. No one would take builds&testing on remote server seriously if there is a need of waiting an hour or even longer for build results. Here you can find some tips&tricks making your builds much faster if you chose gradle as your build tool.

Continue reading “Continuous Integration #1: How to speed up gradle builds”

Best practices #2: Why QA’s are hypocrites

The role of a quality engineer in many companies is not only testing features or implementing automation tests but introducing best coding practices and mentoring team how to test software. They (we actually) are telling developers how good coverage is important and almost force them to implement unit tests wherever it’s possible. And we all know that it’s a good approach. We all know that every production or reused code should be tested. But wait… Are testers who say so much about unit testing and coverage follow principles they enforce? Continue reading “Best practices #2: Why QA’s are hypocrites”

Conference review #1: SkładQA 2018

Is it possible to organize conference for over 600 people without any budget, any sponsors and any company behind with only few people on the board? KraQA team says yes and for the third time has organized SkładQA – absolutely free, software quality conference. We had an opportunity to see in action best speakers talking about most up-to-date challenges in software testing and quality assurance, drink tasty beers and eat some food in cheerful place which Stara Zajezdnia in Cracow definitely is. Continue reading “Conference review #1: SkładQA 2018”

Best practices #1: Test quarantine

Many companies have a lot of regression tests but quite often are struggle with bunch of them failing every build or from time to time (flaky tests). Sometimes it is 25% or more of all of automation tests. What should you do as „quality” engineer in this situation? Should you stop deployment for months until you and your team to fix all of unstable and failing tests or should you manually check every single failure before every release to production? Or maybe you should just ignore it and wait till the situation will improve somehow itself? Continue reading “Best practices #1: Test quarantine”

Learning #1: Conferences in 2018

By entering the IT world everyone needs to face the same problem: where to find best sources and materials for  learning. This industry is growing so fast that it’s hard to rely on books written 10 or more years ago. There are some exceptions but still most books are highly theoretical and you need some practical knowledge. That is why most of us are learning on the internet reading articles, blogs and tutorials. But there is another way which I recommend to try: conferences and meetups. Continue reading “Learning #1: Conferences in 2018”

Meetup review #1: Component testing of React.js applications with Enzyme – KraQA #29

It is quite easy to notice that end-to-end testing with javascript based frameworks is a trend right now. More and more tools appears on the market. Let’s just name Protractor, Enzyme, Nightwatch, Cypress… But are they just another fancy technologies that you can put into your CV or is it really make sense to transform testing stack into js? Continue reading “Meetup review #1: Component testing of React.js applications with Enzyme – KraQA #29”