Testing HTML Emails using Cypress

In this blog post, we will use a local SMTP server to receive emails sent by the app to the user. We will test the HTML emails to make sure they look and work correctly.

Note: you can find the source code shown in this blog post at cypress-email-example and watch a video explaining the testing process here.

Sending emails

If you want to send an email from a Node program, I would suggest using the nodemailer module. Here is an example script to send an email via a local SMTP server

In the production system the host and the port would be your organization’s production SMTP server. But when testing locally, let’s assume the email server is running at localhost:7777. We can make the email-sending code reusable:

Any part of our application can thus require the above module and use it to send an email:

Great, now let’s receive an email.

Receiving emails

During testing, we want to use a local STMP server that would give us access to the received emails. A simple implementation can be found in the smtp-tester NPM module. Let’s create the server and print every incoming message:

Start the server and then execute the send.js script

The mail server prints the detailed email information

The received email contains both the plain text and the “rich” HTML bodies we have sent.

The application

Imagine you have an application where the user enters their email and the application emails the confirmation code to the user.

The registration page

The user must enter the sent code into the “confirm” page.

The confirmation page expects the emailed code

In our case, the application receives the registration form inputs from the front-end as a JSON object. The backend function uses the email utility we wrote above to send the actual (hardcoded for now) confirmation code.

The confirmation page can call the backend with the user-submitted code, or in my demo it simply verifies the input against the expected string “654agc”.

The confirmation page shows success message if the code is valid

Confirmation page test

As the first step, let’s confirm the above page works - it should show an error message for an invalid code, and a success message for the valid one. Our Cypress test can be this:

The test passes

The STMP server inside Cypress

During testing we want to receive the email the application is sending. Thus we need access to the SMTP server receiving the emails - Cypress can spawn such server using the smtp-tester module right from its plugin file! The plugin file runs in Node, thus it can bind to the local socket, listen for the incoming SMTP messages - yet be accessible from the test via cy.task command.

The SMTP server will start when we run Cypress. Now we can write a test to fill the registration page form and submit it - we should see the email arrive.

The above test:

• visits the registration page
• fills the registration form: name, email, company size
• clicks the submit button and checks the application ends up at the /confirm page
• spies on the network call using cy.intercept command to make sure the application does send the registration information to the backend

#tutorials #html #emails #cypress

What is GEEK

Buddha Community

Testing HTML Emails using Cypress

In this blog post, we will use a local SMTP server to receive emails sent by the app to the user. We will test the HTML emails to make sure they look and work correctly.

Note: you can find the source code shown in this blog post at cypress-email-example and watch a video explaining the testing process here.

Sending emails

If you want to send an email from a Node program, I would suggest using the nodemailer module. Here is an example script to send an email via a local SMTP server

In the production system the host and the port would be your organization’s production SMTP server. But when testing locally, let’s assume the email server is running at localhost:7777. We can make the email-sending code reusable:

Any part of our application can thus require the above module and use it to send an email:

Great, now let’s receive an email.

Receiving emails

During testing, we want to use a local STMP server that would give us access to the received emails. A simple implementation can be found in the smtp-tester NPM module. Let’s create the server and print every incoming message:

Start the server and then execute the send.js script

The mail server prints the detailed email information

The received email contains both the plain text and the “rich” HTML bodies we have sent.

The application

Imagine you have an application where the user enters their email and the application emails the confirmation code to the user.

The registration page

The user must enter the sent code into the “confirm” page.

The confirmation page expects the emailed code

In our case, the application receives the registration form inputs from the front-end as a JSON object. The backend function uses the email utility we wrote above to send the actual (hardcoded for now) confirmation code.

The confirmation page can call the backend with the user-submitted code, or in my demo it simply verifies the input against the expected string “654agc”.

The confirmation page shows success message if the code is valid

Confirmation page test

As the first step, let’s confirm the above page works - it should show an error message for an invalid code, and a success message for the valid one. Our Cypress test can be this:

The test passes

The STMP server inside Cypress

During testing we want to receive the email the application is sending. Thus we need access to the SMTP server receiving the emails - Cypress can spawn such server using the smtp-tester module right from its plugin file! The plugin file runs in Node, thus it can bind to the local socket, listen for the incoming SMTP messages - yet be accessible from the test via cy.task command.

The SMTP server will start when we run Cypress. Now we can write a test to fill the registration page form and submit it - we should see the email arrive.

The above test:

• visits the registration page
• fills the registration form: name, email, company size
• clicks the submit button and checks the application ends up at the /confirm page
• spies on the network call using cy.intercept command to make sure the application does send the registration information to the backend

#tutorials #html #emails #cypress

Commonly Used HTML Tags with Examples

HTML tags are keywords used in HTML to display web-pages with certain properties. They are further used for defining HTML elements. An HTML element consists of a starting tag, some content, and an ending tag. The web browser reads the HTML document from top to bottom, left to right. Each HTML tag defines a new property that helps in rendering the website.

HTML Tags

The ‘<>’ brackets contain an HTML tag. There are two types of HTML tags- empty tags or singleton tags and container tags. Singleton tags or empty tags do not contain any content such as an image or a paragraph and hence do not need to be closed, whereas container tags should be closed.

Syntax

1. Some Content

Examples of:

Empty tag: 
,

---

,etc.

Container tags: 

Paragraph

Link

1. <!DOCTYPE>

4. Paragraph

5. Heading

6. Bold
7. Italic
8. Underline

Output-

Head tags:

#html tutorials #html image tags #html link tags #html list tags #html tags #html

Testing Microservices Applications

The shift towards microservices and modular applications makes testing more important and more challenging at the same time. You have to make sure that the microservices running in containers perform well and as intended, but you can no longer rely on conventional testing strategies to get the job done.

This is where new testing approaches are needed. Testing your microservices applications require the right approach, a suitable set of tools, and immense attention to details. This article will guide you through the process of testing your microservices and talk about the challenges you will have to overcome along the way. Let’s get started, shall we?

A Brave New World

Traditionally, testing a monolith application meant configuring a test environment and setting up all of the application components in a way that matched the production environment. It took time to set up the testing environment, and there were a lot of complexities around the process.

Testing also requires the application to run in full. It is not possible to test monolith apps on a per-component basis, mainly because there is usually a base code that ties everything together, and the app is designed to run as a complete app to work properly.

Microservices running in containers offer one particular advantage: universal compatibility. You don’t have to match the testing environment with the deployment architecture exactly, and you can get away with testing individual components rather than the full app in some situations.

Of course, you will have to embrace the new cloud-native approach across the pipeline. Rather than creating critical dependencies between microservices, you need to treat each one as a semi-independent module.

The only monolith or centralized portion of the application is the database, but this too is an easy challenge to overcome. As long as you have a persistent database running on your test environment, you can perform tests at any time.

Keep in mind that there are additional things to focus on when testing microservices.

• Microservices rely on network communications to talk to each other, so network reliability and requirements must be part of the testing.
• Automation and infrastructure elements are now added as codes, and you have to make sure that they also run properly when microservices are pushed through the pipeline
• While containerization is universal, you still have to pay attention to specific dependencies and create a testing strategy that allows for those dependencies to be included

Test containers are the method of choice for many developers. Unlike monolith apps, which lets you use stubs and mocks for testing, microservices need to be tested in test containers. Many CI/CD pipelines actually integrate production microservices as part of the testing process.

Contract Testing as an Approach

As mentioned before, there are many ways to test microservices effectively, but the one approach that developers now use reliably is contract testing. Loosely coupled microservices can be tested in an effective and efficient way using contract testing, mainly because this testing approach focuses on contracts; in other words, it focuses on how components or microservices communicate with each other.

Syntax and semantics construct how components communicate with each other. By defining syntax and semantics in a standardized way and testing microservices based on their ability to generate the right message formats and meet behavioral expectations, you can rest assured knowing that the microservices will behave as intended when deployed.

Ways to Test Microservices

It is easy to fall into the trap of making testing microservices complicated, but there are ways to avoid this problem. Testing microservices doesn’t have to be complicated at all when you have the right strategy in place.

There are several ways to test microservices too, including:

• Unit testing: Which allows developers to test microservices in a granular way. It doesn’t limit testing to individual microservices, but rather allows developers to take a more granular approach such as testing individual features or runtimes.
• Integration testing: Which handles the testing of microservices in an interactive way. Microservices still need to work with each other when they are deployed, and integration testing is a key process in making sure that they do.
• End-to-end testing: Which⁠—as the name suggests⁠—tests microservices as a complete app. This type of testing enables the testing of features, UI, communications, and other components that construct the app.

What’s important to note is the fact that these testing approaches allow for asynchronous testing. After all, asynchronous development is what makes developing microservices very appealing in the first place. By allowing for asynchronous testing, you can also make sure that components or microservices can be updated independently to one another.

#blog #microservices #testing #caylent #contract testing #end-to-end testing #hoverfly #integration testing #microservices #microservices architecture #pact #testing #unit testing #vagrant #vcr

Know Everything About HTML With HTML Experts

HTML stands for a hypertext markup language. For the designs to be displayed in web browser HTML is the markup language. Technologies like Cascading style sheets (CSS) and scripting languages such as JavaScript assist HTML. With the help of HTML websites and the web, designs are created. Html has a wide range of academic applications. HTML has a series of elements. HTML helps to display web content. Its elements tell the web how to display the contents.

The document component of HTML is known as an HTML element. HTML element helps in displaying the web pages. An HTML document is a mixture of text nodes and HTML elements.

Basics of HTML are-

The simple fundamental components oh HTML is

1. Head- the setup information for the program and web pages is carried in the head
2. Body- the actual substance that is to be shown on the web page is carried in the body
3. HTML- information starts and ends with and labels.
4. Comments- come up in between

Html versions timeline

1. HTML was created in 1990. Html is a program that is updated regularly. the timeline for the HTML versions is
2. HTML 2- November, 1995
3. HTML 3- January, 1997
4. HTML 4- December, 1997; April, 1998; December, 1999; May, 2000
5. HTML 5- October, 2014; November, 2016; December, 2017

HTML draft version timelines are

1. October 1991
2. June 1992
3. November 1992
4. June 1993
5. November 1993
6. November 1994
7. April 1995
8. January 2008
9. HTML 5-
   2011, last call
   2012 candidate recommendation
   2014 proposed recommendation and recommendation

HTML helps in creating web pages. In web pages, there are texts, pictures, colouring schemes, tables, and a variety of other things. HTML allows all these on a web page.
There are a lot of attributes in HTML. It may get difficult to memorize these attributes. HTML is a tricky concept. Sometimes it gets difficult to find a single mistake that doesn’t let the web page function properly.

Many minor things are to be kept in mind in HTML. To complete an HTML assignment, it is always advisable to seek help from online experts. These experts are well trained and acknowledged with the subject. They provide quality content within the prescribed deadline. With several positive reviews, the online expert help for HTML assignment is highly recommended.

#html assignment help #html assignment writing help #online html assignment writing help #html assignment help service online #what is html #about html

7 Easy Steps to Generate both JUnit XML and HTML reports with Cypress

The common requirement when we are working with automation tests in we need to generate both XML and HMTL reports. When it comes to Cypress it relies on Mocha awesome reporter. In this article, I will explain to you a simple way to generate HTML and Junit XML reporter in your Cypress end-to-end Automation framework.

If you look over the internet there are many articles but for beginners, it’s very complicated Since there is some complexity involved.

This tutorial also answers the Questions commonly searched on the internet

How to Generate XML and HTML files in Cypress?

How to configure HTML and XML files with cypress?

How to Integrate HTML and XML files with Cypress?

How to Generate and Merge Junit XML file using mocha Junit reporter in Cypress?

How to Configure reports into Cypress End to End Automation framework?

This article also talks about merging Junit XML file into a single file

Let’s get started.

Generating both XML and HTML reports with Screenshots and Merging all XML files in Cypress

Assumptions:

Here the assumption is you have already working cypress framework and you are looking for integrating both Junit and HTML reports into your cypress.

#html #xml #cypress #beginner #cypress #html