Showing 10
Showing 10
In today’s competitive environment, you are either different, or you are the cheapest. And innovation is necessary to be different.
That is why innovation has become one of the strategic priorities of major companies. Year after year we see how budgets in this area are rising; however, many companies are facing a harsh reality: The investment is not translating into results.
Traditional companies, designed to think about operational efficiency, are now forced to move on to a new terrain for which they are not prepared: the grounds for change.
In the previous posts I wrote about the main considerations to be kept in mind when structuring the app to be easily testable, and identified the main concepts and tools.
We also got to work and implemented a series of unit and integration tests using the most common Mockito tools and functions.
To finish this series of posts, we will now see the so called instrumented tests, which is the basis for the UI tests.
In addition, as we already mentioned in previous posts, it is also a great tool for End-to-End tests and any other test that requires working with the app as a whole.
If you did not read the first part “Android Testing with Kotlin, Mockito and Espresso” I recommend you take a quick look before continuing with this, because I will mention some things that came in it.
In this second instalment, we will see unit tests in greater detail. As already said, developing unit tests and integration tests is very similar and the difference lies in the number of entities, layers and/or scenarios involved in the functionality being tested. To clarify this, we will look at examples of both.
The purpose of this post is to be much less theoretical than the previous one and get our hands dirty, so that we quickly review some good practices when implementing a series of inter-related tests and look at the main functions offered by JUnit and Mockito, at least those that we have found most useful in the teams I have worked in.
Of course, there are many valid ways to face the tests of a given functionality and I certainly do not intend to imply that this is the most correct one, but I think it is a good starting point so that each one of you can later refine your own styles.
As the title of the post says, the idea is to give you a boost to begin with, but it is up to you to research more and get even more out of it.
If you are involved in the development of mobile apps, it will surely not surprise you if I tell you that for years I have met dozens of good programmers that, however, have spent little (or nothing) on testing their apps. I will not lie to you; I was one of them for a long time!
Perhaps because they are “lightning projects” and times are so tight that they do not allow more than “painting screens” as soon as possible, or perhaps because the possibility of doing manual tests is so in the palm of our hands (literally in this case) that have led us to believe testing is a kind of unnecessary luxury…
In any case, the truth is that finding apps with a good test base is not as common as it should be in a professional development environment.
The objective of this post is to make a quick introduction to the implementation of Android app oriented tests, so that any colleagues wishing to leave that group and take a step further have a small initial guide.
If something made Big Data Spain 2018 special for us was the great amount of technologies and tools we discovered. We were lucky to have great Spanish and foreign industry speakers that told us about the latest developments on the market.
What will be the next frameworks with which we will work? What technologies will revolutionize the digital world as we know it today? At Big Data Spain 2018 we took a small leap into the future and realized we cannot lose sight of the short term. What will the next big things be in the near future?
Digital transformation entails changing the organization and relational flow of companies: It is a new way of thinking and working at the business level that goes beyond technology and must also transform their culture and work methodology.
Nowadays trends and changes in user habits are forcing companies to undergo a digital adaptation where digital processes and products will never cease to move forward.
However, we must take this transformation one step further and put users at the centre of our strategy, since they will be the ones that will bring us value and set us apart in such a changing world.
Every digital transformation must go hand in hand with a digital strategy that maximizes the satisfaction of our clients and enables us to achieve the marketing and business goals in our channels.
In a multicloud world that is dominated by the big three providers – Amazon Web Services, Google Cloud and Microsoft Azure – why choose a single Cloud provider when you can enjoy everything they offer?
Broader and more varied products are increasingly made available to us, but they all are high quality services with excellent availability, top-notch security and high performance, so they are going to allow us to meet any need we might have.
Of course, they differ in name, price, technology and how they are grouped within each platform. We are going to compare the services of the big three public clouds to see which one is better for us.
How many times have you heard about Blockchain and DLT in the past few months? A lot, right? In this post we want to give you another alternative to this type of technologies.
Although it has some of Blockchain’s features, it also has some particularities that make all the difference in certain IoT-based use cases. Today we are going to talk bout IOTA.
Many people believe that software quality should be based on testing the code delivered by each developer but we at Paradigma think this is not correct. Quality is built up from the earliest stages and should not be ignored in any phase – until the last day of the project.
If we were to ask people working for many companies that boast about the quality of their products, they probably would not know what to tell us about what they really do to work on that quality.
Paradigma not only encourages us to work with the latest technologies but also us to do so striving to achieve more quality at all times.
That is why we at the QA team have defined 6 key points that help us turn our projects into success cases.
Actionable data are the key to success for any online store. If you have been running an ecommerce business, you may already be aware of how important data-driven ecommerce marketing is.
In this post we are going to go over the benefits of setting up ecommerce tracking in Google Analytics. In addition, this process can also be applied to the earliest stages of e-stores. Let’s go!
