<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Javascript on Hugo Bootstrap</title>
    <link>/en/categories/javascript/</link>
    <description>Recent content in Javascript on Hugo Bootstrap</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright © 2016-{year} Razon Yang. All Rights Reserved.</copyright>
    <lastBuildDate>Sat, 21 Aug 2021 09:00:00 +0000</lastBuildDate><atom:link href="/en/categories/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Spying (on) Methods with Jest</title>
      <link>/en/posts/2021-08-25-spying-on-methods-jest/</link>
      <pubDate>Sat, 21 Aug 2021 09:00:00 +0000</pubDate>
      
      <guid>/en/posts/2021-08-25-spying-on-methods-jest/</guid>
      <description>How mocks make it easy to ensure your application logic It&amp;rsquo;s easy to test your application when your domain layer is decoupled from other:
For example, let&amp;rsquo;s imagine the following scenario:
 In a Race Game, when the Car hit an obstacle, the player will go back a couple of yards, and the barrier will be removed
 The Pseudo-code We have a Game class that receives the Player and the ObstacleManager:</description>
    </item>
    
  </channel>
</rss>
