BACK
# | Module name | Technical requirement | Test Case ID's | Total |
---|---|---|---|---|
1 | Web Main Page - Recruiters | The landing page for recruiters must display key product features, a comparison with competing platforms, a CEO quote, and partner logos.<br><br>The design should encourage sign-up and navigation to the candidate list. | C416, C422, C424, C425, C413 | 5 |
2 | Web Main Page - Engineers | Homepage for engineers (unauthenticated users) must contain a registration form with email and social login options (Google, LinkedIn, GitHub).<br>Logged-in users should see a promotional mobile app banner instead of the form.<br>The bottom of the page must show a minimum of 10 authentic user reviews.<br>Homepage must contain links to the Jobs and Web3 Companies pages. | C462, C407, C409, C398 | 4 |
3 | Web Candidates List | The candidate list must display candidate cards with a brief summary of their skills and achievements.<br>Clicking 'Show experience' expands detailed experience data.<br>Filters (role, technology, salary, English level, location) must be visible to all users but usable only by logged-in recruiters.<br>Contact info must remain hidden until a chat is started.<br>Recruiters can initiate chats only after profile creation. | C431, C435, C430, C432, C434, C433 | 6 |
4 | Web Sign Up - Recruiter | Recruiters must be able to register using email or social logins (Google, LinkedIn, GitHub).<br>The process includes entering personal, company, and contact details, as well as defining candidate preferences (role, technology, salary, experience, English level, location).<br>After registration, the recruiter is redirected to the candidate list. | C439, C443, C444, C445, C446, C447, C440, C463 | 8 |
5 | Web Sign Up - Candidate | Recruiters must be able to register using email or social logins (Google, LinkedIn, GitHub).<br>Candidates must complete a 5-step registration process: <br>1) role and skills, <br>2) expectations (salary, experience, location, English level), <br>3) experience (import from LinkedIn optional), <br>4) bio and career goals, <br>5) contact info including photo, CV, and social links.<br>Profile becomes active after admin approval (24–48 hours). | C439, C443, C444, C445, C446, C447, C441, C442 | 8 |
6 | Web Sign In | The login page must include link to the registration page.<br>The login page must include link to the 'Forgot Password'.<br>Upon successful login with valid credentials, users access their dashboard.<br>Incorrect credentials must trigger a clear error message. | C448, C451, C449, C450 | 4 |
7 | Web Chats | Candidates can accept or decline contact sharing.<br>Recruiters can start chats with candidates via the candidate list or profile view.<br>Contact details remain hidden until the chat is initiated.<br>Recruiters can send offers, archive or favorite chats. | C400, C433, C434, C469 | 4 |
8 | Web Profile - Candidate | Candidates must be able to view and edit their profile details (name, photo, social links, bio, experience).<br>The interface must allow toggling profile visibility and saving changes with preview functionality. | C399, C470, C471, C472, C473, C475 | 7 |
9 | Profile - RecruiterWeb | Recruiters must be able to edit their profile including personal details, photo, and social media links.<br>All updates must be saved and visible immediately in the profile view. | C476, C477, C478, C479 | 4 |
10 | Web Footer | The footer must include: <br>1) a preview section of the 'TOP 100 WEB3 COMPANIES' (top 5 visible), <br>2) three columns of categorized job offers for developers, <br>3) social media links (LinkedIn, Twitter, Telegram, etc.),<br>4) links to documents, pricing, FAQ, and About Us pages. | C407, C404, C428, C437, C438 | 5 |
11 | Web3 Companies and Jobs | Users must be able to navigate to Web3 Companies and Jobs from homepage.<br>Applying with 1 click should be available for authorized users.<br>The Web3 Companies page must include a table of 100 companies with pagination (10 per page).<br>Each row should contain a clickable name and logo leading to the company’s job listings.<br>Logged-in users can add jobs manually or via ATS import.<br>Guests can view limited listings and are prompted to log in for full access.<br>Subscription form is available at the bottom.<br>Users must be able to search for jobs using keywords and filters. | C407, C402, C460, C456, C480, C481, C483, C484, C452, C482, C453, C485, C486, C487, C488 | 8 |
12 | Mobile Launch Screen | The mobile app MVP must auto-redirect to login after splash screen. | C128, C129 | 2 |
13 | Mobile Registration | The mobile app MVP must support registration (email, Google). | C130, C131, C198 | 3 |
14 | Mobile Login | The mobile app MVP must support login (email, Google) and password reset. | C133, C134, C135, C136, C137, C138 | 6 |
15 | Mobile Chat | The app must support basic chat functionalities: view chat list, send/receive messages, toggle between ALL and ARCHIVE tabs, and search chats. UI elements must reflect role-based access (candidate or recruiter). | C139, C140, C141, C142, C180, C181, C182, C183 | 8 |
16 | Mobile Profile | The mobile profile module must allow users to view and update profile data (name, avatar, contact info, social links) and manage notification settings. <br>The candidate and recruiter profiles must be editable separately. Changes should apply instantly. | C143, C144, C145, C147, C148, C149, C184, C185, C186, C187, C150, C151, C152, C153, C154, C155, C189, C156, C157, C158, C159, C160, C161, C162, C163, C164, C165, C166, C167, C168, C169, C170, C171, C172, C173, C174, C190, C191, C192, C193, C175, C177, C194, C197, C176, C196 | 46 |
17 | Mobile Privacy Policy | The mobile app must provide access to app privacy policy, and terms. | C132, C179, C195 | 3 |
18 | Mobile Sign Out | The mobile profile module must allow users to sign out. | C188, C178 | 2 |
BACK