Posted on

Tests Plan – Quality Assurance – Testing Software (Part 1)

In this article I’ll  share my thoughts and experience about a possible  list of testing artefacts that could help to improve the quality assurance in the software development working with test plan.

checklist

Before to see the different test plans It’s important to know so basic artefacts like :

  • Test Case: List of  steps in order to cover only one application scenario where the test case should have a descriptive title of the scenario and describe the result of each step
  • Test Results: evidence of  execution of a test case
  • Test Plan: is a group of test cases
  • Regression Test: used to test the regression produced an existent  feature
  • Smoke Test:  list of steps to cover quickly different features without enter in details.
  • Automation: Not all the Test Cases could or should be automated.
    There are different ways to automated the test cases using : unit test, integration test, client side unit test or UI test)

Ads: curso práctico de testing automático presencial y también online

There are  different test plans like :

Continue reading “Tests Plan – Quality Assurance – Testing Software (Part 1)”

Posted on

Automate Manual Regression Test Plan – (Testing thoughts Part 1 of N)

In this simple article, I want to share some thoughts about how to automate  a manual regression test plan . I did a simple poll where I asked :

Which tool/framework do you use to automate the execution of a full manual regression test plan to validate business scenarios ?

Before answering, you should think about the “Ice-cream testing cone”

ICECREAMCONE_TEST

Ice-cream cone : If you are testing through the User Interface (UI) them it will be slow, increasing build times. For more information please click on this article by Martin Fowler.

Ads: curso práctico de testing automático presencial y también online

From the previous image, it is clear that it is not a good idea to invest much time building a huge collection of UI Tests and here we have the results of the Poll :

Continue reading “Automate Manual Regression Test Plan – (Testing thoughts Part 1 of N)”

Posted on

Support Workflow: Gathering customers information to save time to solve tickets – Tools – (Part 1 of N)

It’s very common when a company start to increase the number of customers It’ll be probably increased the number of support’s tickets.

When I usually worked helping to the last line of support I saw for many tickets always was asked to the customers similar questions. I usually tried get from the customers configuration files , logs to know more information in order to progress the ticket .

Don’t you think this support workflow of retrieve the customer information could be improved it?

I think it could be automated the gathering information so when the customer will raise a new ticket it could be also attached the relevant information obtained from an automated tool .

With this approach we’ll have an “all in one ticket” because the ticket will have all the relevant information so it will saved time in both side .

business-customer-care-service_1325-159

Ads: curso práctico de testing automático presencial y también online

Here we have some reasons why I think we should try to improve the support process workflow in order to

Continue reading “Support Workflow: Gathering customers information to save time to solve tickets – Tools – (Part 1 of N)”

Posted on

Business Layer Software Architecture (Part 2 of N)

In a previous article about “Layered Software Architecture Part 1″ I shared my thoughts about it isn’t enough just applying any of the MvC, MvvM or MvP patterns to build a good Software Architecture.

In this simple article I just wanted share my thoughts about the business logic layer in a N-Tier architecture . I think the Business Layer will have more sense when it will be required to add some pure business logic in the software and it won’t be much useful for simple CRUD applications.

For non CRUD applications where there are business logic in the app I think it’s a good idea if  :

  • Api Rest (Communication) Layer shouldn’t have business logic neither have  access directly to the Data with an ORM.
  • Api Rest (Communication) Layer should only limited to have simple data validations.
  • Business layer should avoid to have direct access to data via ORM or SqlQueries since the Data Access Layer is the responsible
  • We should try to build thin Api Rest (Communication) Layer and fat Business Logic Layer

responsibility

Here below we have a list of points of what I think it should be done  in business logic :

Continue reading “Business Layer Software Architecture (Part 2 of N)”

Posted on

Building release notes in agile development

Many Development Teams are working with scrum creating at least one new software version every three weeks . This workflow including a new version of documentation every three week.

Did we ask us if we should change how do we generate release notes ?

The number of released software versions is increasing using this type of agile methodologies but Don’t you think it’s time to change this?

 

Continue reading “Building release notes in agile development”

Posted on

Layered Software Architecture (Part 1 of N)

There are different architecture patterns like MVC , MVP or MvvM but I’m convince that it’s required more artefacts to build a good Software Architecture.

Do you think if it’s enough just applying any of the previous patterns to build a good Software Architecture ?

mvc_mvp_mvvm_

MVC , MVP or MvvM are architecture patterns to structure code and those patterns was common has been used by Developers with experience to reduce the coupling between layers.

For example:

Continue reading “Layered Software Architecture (Part 1 of N)”