forked from kamranahmedse/developer-roadmap
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add content for CSR/SSR, Caching and UAT. (kamranahmedse#2505)
* [kamranahmedse#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 <[email protected]>
- Loading branch information
1 parent
80296dc
commit f042739
Showing
3 changed files
with
14 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 6 additions & 1 deletion
7
...-qa-automated-testing/100-frontend-automation/100-basic-introduction/caching.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,6 @@ | ||
| # Caching | ||
| # 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> |
8 changes: 7 additions & 1 deletion
8
...-automated-testing/100-frontend-automation/100-basic-introduction/csr-vs-ssr.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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> |