Servage Magazine

Information about YOUR hosting company – where we give you a clear picture of what we think and do!

Articles Tagged ‘testing’

Synchronized Browser Testing with Browsersync

Sunday, February 19th, 2017 by Servage
browsersyncBrowsersync is a testing tool that makes it possible to test web applications using multiple browsers and devices at the same time. You control one browser, and everything you do is replicated on other connected devices. You can scroll, fill out forms, click links and do much more with Browsersync. This makes it much faster to test websites, and you will also notice rendering differences between browsers easier. Browsersync Explained in More Detail Browsersync is a NodeJS module that can be installed using NPM, the package manager for NodeJS. Having said that, NodeJS and NPM must be installed to use it. We will not be covering the installation of these two in this ...

Automating testing with continuous integration

Friday, December 16th, 2016 by Servage
Continous-IntegrationIf you are writing tests for your application or your application must be prepared for release each time a new version is created, you should be using continuous integration (CI). It allows you to automate both of these processes by triggering them whenever you want, such as when you push a commit to a Git repository. Continuous integration can save you a lot of development time, and this is how you can get started. Why Continuous Integration? If your application is still in development, probably the biggest advantage in CI is the ability to automatically run tests for new features. You can also use it to build your application from source code into ...

Working with acceptance testing

Saturday, December 3rd, 2016 by Servage
AcceptanceTestingSoftware testing is important, and hopefully all developers agree with it. Finding a bug at an early stage is much easier and cost-effective to solve than letting it go unnoticed for a long time. But how does testing a web application work? Let's look into one way to do it: Acceptance Testing. Acceptance Testing explained Acceptance testing means the process of testing that an application works as it should. In a web application it works by clicking buttons, submitting forms and tweaking settings. Acceptance testing is usually the last step of testing. If you have different types of tests, you usually run unit and functional tests before acceptance tests. In acceptance testing, the tester ...

Functional testing with Codeception

Saturday, November 5th, 2016 by Servage
Functional-testingCodeception is a tool that can be used to automate the testing process of web applications. You can use it to write various types of automated tests, and this time we will focus on functional tests. You will learn two things: What functional tests are, and how to write them. What is functional testing? Let us first briefly get familiar with the concept of functional testing. Functional testing is one of the many software testing methods that allows you to verify that your application meets its requirements and does what it should do. In unit tests you test a small individual piece of code in your application. A functional test takes those small ...

Split-testing answers your unsolved questions

Saturday, November 15th, 2014 by Servage
Split_testingSplit-testing is the method of placing different ideas for the same components on a web page, to test and thereby know which one will work the best to increase conversion. Therefore, if you know your weaker links and know how to overcome them the best way using A/B testings, you definitely will have a greater chance at winning the battle of conversion optimization at first hand. Conversion optimization is a vast subject to cover in a single post as numerous books are devoted to this subject alone. Therefore this post will focus on the split-test or A/B testing of landing pages and its role in conversion itself. We have very complex websites today in terms ...

Model-based validation with Eloquent

Friday, November 14th, 2014 by Servage
ImageIn some opinions the lack of model-based validation is one of the major deficits with Eloquent models in the Laravel PHP framework. One side argues that it pollutes the core model code by implementing lots of rarely used functionality - which the other side counters with the opposite argument: It's needed in the core model, because it is commonly used functionality. However, even if agreeing on making validation model-based, the next discussion would be about the implementation. It would therefore be great for the Laravel community to overcome this discussion, and implement a widely accepted model-based validation principle. In the meantime you can be inspired by the implementation below - of not only validation ...