Skip to main content

Types of tests [DSP2017 #04]

As a java developer with more than 3 years of experience I had opportunity of participating in few projects. To be honest only in a last one a testing strategy is on high level.  I encourage you for introduce and put more pressure on testing strategy during a delivery process. As with all new things the beginnings are difficult but I'm sure that it is worth.

As almost testers know undermentioned pyramid I need to put it for people who have not seen it.

In a big amount of projects we can meet this pyramid in inverted order. What can impact of quality of a system. For example when we have a lot of manual tests it is boring for users and sometimes they can be skipped what can missed bug.

So in the lowest level we see the Unit tests and the count of this should be the bigger and on the highest level, there are manual tests. As we can expect the count should of them should be the lowest.

A few words about each of them:
  • Unit tests - should be quick and small. They check just one method or part of code.
  • Component tests - should test one module/component/functionality of your project and not depend from other modules.
  • Integration tests - should test a connectivity between components, modules, databases etc.
  • E2E (End to End) tests - should test the all flow from beginning to the end of process.
  • Manual tests - tests which are impossible to automate.


Labels:

Comments

  1. deMarch 15, 2017 at 3:29 PM

    Beautiful theory :: cruel world ;) Did you ever worked with system, where were a lot of automated tests and only few scenarios were tested manually? ;) Best begards (from tester;))

    ReplyDelete
    Replies
    1. SobekMarch 16, 2017 at 4:27 AM

      Thanks for your comment. Yes now we work on this kind of system where we try to automate each new manual test :) I will continue this topic in next posts.

      Delete

Post a Comment

Popular posts from this blog

Jenkins [DSP2017 #06]

In this entry I want to introduce tool which should be used in each projects. It covers how to install and configure a simple job. First of all I started from installation of jenkins in my local machine (Ubuntu). You can download installation package from official page or use jenkins wiki . As like always I met some problem:  The following packages have unmet dependencies:  jenkins : Depends: daemon but it is not installed As a resolving of it I used command apt-get -f install and next apt-get upgrade . Then we should be able see the page like below on address http://localhost:8080 After unlock and installation some pluggins we should be able to see something like below. Next I added simple job which will check the repository and run command gradle -p nany-server test . The result is on an image below. I think that few of us met with lost jobs definitions. What then? We need to define each job manually again. From my point of view the bette...
Post a Comment
Read more

How to start with Android development [DSP2017 #07]

In this part I want to show how I started with a first app. My previous experience with creating an Android application was about 4-5 years ago. I've created one or two simple applications during my studies and forgot about this topic. Today when I wanted to create a new app I needed to start from beginning. First of all I need to install tools: Android Studio (I use Intellij with Android extension). Android SDK - I used the sdkmanager but during Android Studio installation sdk should be installed. If you have 64 bits system you need to check: Required libraries for 64-bit machines . If you have installed all above tools you should be able to create simple Android project and run it on your phone. Yes, like always I met few problems with run the application on my phone. #1 The adb can not find my device. Solution : turn phone as MTP mode. 2# Error:Execution failed for task ':app:processDebugResources'. > com.android.ide.common.process.ProcessException:...
Post a Comment
Read more