Main

type

5 (blog/news article)

status

30 (imported + raw text content deleted)

review version

0

cleanup version

0

pending deletion

0 (-)

created at

2025-04-27 08:23:36

updated at

2025-10-29 02:19:10

pol page id

2077963934

pol status

0

pol hosts ticketing

pol hosts ecommerce

pol hosts finance

pol hosts crypto

pol hosts leak

pol hosts devel

pol hosts ugc

docs.google.com

pol hosts klim

pol hosts builders

pol hosts self subdomains

pol hosts other subdomains

pol hosts other domains

pol updated

1763166929

Address

url

https://devcom.vt.edu/posts/2021/01/mocking-cas-users-in-local-development/

url length

75

url crc

38132

url crc32

3701576948

location type

1 (url matches target location, page_location is empty)

canonical status

2 (missing canonical tag in html)

canonical page id

-

Source

domain id

345221232

domain tld

0

domain parts

0

originating warc id

-

originating url

https://devcom.vt.edu/sitemap.xml

source type

1 (sitemap)

Server response

server ip

18.66.112.26

Publication date

2025-10-29 02:19:10

Fetch attempts

1

Original html size

13517

Normalized and saved size

13242

Content

title

Mocking CAS Users in Local Development – VT DevCom Posts

excerpt

content

At the 2021 IT Symposium, Michael Irwin spoke about the benefits of “persona-driven development”, or the idea of developing personas representing real users for local development and testing (slides are available here). The main benefits are:Everyone on the team has the same mental model of users/roles - when many of our real users wear different hats for the many roles they carry, it’s easy to get different mental models of what each user should be able to do within our applications. By having a consistent set of personas shared by the entire team, we can more easily be on the same page.No longer tied to real auth - if these personas are used in development and testing, we no longer are tied to the lifecycle of real users who change teams, change roles, or change jobs.Supports automated testing - if we can mock users, we can safely include the credentials in our codebase for automated testingA quick warningWhen NOT to mock usersYou MUST NOT mock users in development or testing environ...

author

updated

1763166929

Text analysis

block type

0

extracted fields

105

extracted bits

featured image
title
full content
content was extracted heuristically

detected location

0

detected language

1 (English)

category id

Pozostałe (16)

index version

2025110801

paywall score

0

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

2734

text words

545

text unique words

264

text lines

1

text sentences

10

text paragraphs

1

text words per sentence

54

text matched phrases

0

text matched dictionaries

0