Add content for CSR/SSR, Caching and UAT. (#2505)

* [#1838] Added content for CSR/SSR, Caching and UAT.

* Update content/roadmaps/113-qa/content/103-qa-automated-testing/100-frontend-automation/100-basic-introduction/csr-vs-ssr.md

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>
pull/2503/head^2
Sameer Kumar 2 years ago committed by GitHub
parent 80296dcfb1
commit f042739690
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 1
      content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/uat.md
  2. 5
      content/roadmaps/113-qa/content/103-qa-automated-testing/100-frontend-automation/100-basic-introduction/caching.md
  3. 8
      content/roadmaps/113-qa/content/103-qa-automated-testing/100-frontend-automation/100-basic-introduction/csr-vs-ssr.md

@ -4,3 +4,4 @@ User Acceptance Testing (UAT) is a type of testing performed by the end user or
<ResourceGroupTitle>Free Content</ResourceGroupTitle>
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/user-acceptance-testing.html'>What is User Acceptance Testing (UAT)?</BadgeLink>
<BadgeLink badgeText='Watch' href='https://www.youtube.com/watch?v=AU8SV7091-s'>How to plan your UAT</BadgeLink>

@ -1 +1,6 @@
# Caching
Caching ensures that the resources downloaded once are reused instead of doing a fresh fetch again. It is useful for increasing subsequent page load speed by reusing cached images, fonts, and other static assets. Caching should not be typically done on dynamic content. For example list of posts or comments. As part of the testing strategy, both caching and cache invalidation (not getting stale dynamic content) needs to be tested.
<ResourceGroupTitle>Free Content</ResourceGroupTitle>
<BadgeLink badgeText='Watch' href='https://www.youtube.com/watch?v=6FyXURRVmR0'>Caching - Simply Explained</BadgeLink>

@ -1 +1,7 @@
# Csr vs ssr
# CSR vs SSR
CSR stands for Client Side Rendering and SSR stands for Server Side Rendering. CSR pages are computed in your machine and then shown by your browser while in the case of SSR, the server sends ready to show Html content directly. Primarily React, Vue, and Angular apps are examples of CSR (technically it is possible for them to be executed in SSR mode too) and almost all older tech stacks are SSR like PHP, ruby on rails, java, dot net, etc. From the user's standpoint, CSR apps take higher time to render but compensate by avoiding page reloads later (SPA) while SSR apps often have faster initial load time but do a full page reload often.
<ResourceGroupTitle>Free Content</ResourceGroupTitle>
<BadgeLink badgeText='Watch' href='https://www.youtube.com/watch?v=rNVcZklcmqU'>Server Side Rendering vs Client Side Rendering</BadgeLink>
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://medium.com/@prashantramnyc/server-side-rendering-ssr-vs-client-side-rendering-csr-vs-pre-rendering-using-static-site-89f2d05182ef'>SSR vs CSR vs SSG</BadgeLink>
Loading…
Cancel
Save