kenthu / human-interest-verifier

This tool performs basic verification on how Human Interest reinvests your 401(k) funds after your company migrates from another 401(k) provider

Human Interest 401(k) Verifier

This tool performs basic verification on how Human Interest reinvests your 401(k) funds after your company migrates from another 401(k) provider. I created this tool after finding mistakes in calculations when my 401(k) was migrated from ADP to Human Interest.

Try it out: https://human-interest-verifier.vercel.app/

Tech Stack

This web tool has no back end, to simplify deployment. I used the following languages, tools, and frameworks:

• Next.js React Framework
• written in TypeScript
• tested with Jest
• deployed to Vercel
• linted with ESLint
• Bootstrap
• Font Awesome

This repo also includes a tool to import historical mutual fund prices.

• written in Ruby
• linted with RuboCop

Getting Started

Requirements

• Node.js 18
• Yarn

Installing

1. Clone repository

   git clone https://github.com/kenthu/human-interest-verifier.git
   

2. Install dependencies

   cd human-interest-verifier
   yarn install
   

Running Development Web Server

1. Start server

   yarn dev
   

2. Open http://localhost:3000/

Run Test Suite

yarn test

Importing Mutual Fund Prices

Requirements

• Ruby 2.7+ (tested with both 2.7.4 and 3.0.2)

Running Importer

cd fund_price_importer/
./import.rb

Considerations for Roadmap

• Set up end-to-end testing (Cypress? Playwright?)
• Set up CI/CD
• Use Lighthouse to optimize performance, accessibility, etc.

Known Issues

• This tool is dependent on how Human Interest displays transaction data on its web app, and thus, may break if Human Interest makes changes.

human-interest-verifier's Issues

Some Playwright E2E tests fail unless run in UI mode

When run in UI mode (yarn test:e2e --ui), the entire Playwright E2E test suite passes. But when run otherwise (yarn test:e2e or yarn test:e2e --headed), any tests depending on paste functionality fail.

I'll leave as is for now, since I'm not using using CI to block deploys if tests fail, so the tests are still useful even if they have to be run manually from the GUI.

If this feature (microsoft/playwright#15860) gets added, we could rewrite these tests to use the official API.

If we need to, there is basic support for pasting by simulating CMD+V (microsoft/playwright#8114 (comment)), so we could potentially do something where we create a textarea with the clipboard contents we want, copy it, then paste it. Example: microsoft/playwright#15860 (comment)