Arbeidsflate Test Script Teamtest August 2025 V1.1 Guide
Hey guys! Let's dive into this test script for the Arbeidsflate (Workspace) team test in August 2025. This guide will walk you through each test case, ensuring we cover all the bases. Remember, this test uses the Tenor user: xx80xxyyyyy. We'll go through the cases in order: A, B, C, D, E, F, G, and X.
Before You Start
First things first, make sure this test script is assigned to you. Also, jot down the platform you're testing on (PC, Mac, Android, iPhone, Chromebook) and the browser you're using (Chrome, Edge, Safari, Firefox). This info helps us track down any platform-specific issues.
During the Test
For each test step, leave a comment. Seriously, document everything! This includes when you start a test step, your expectations about the outcome, and the final result. If you spot something related to a dialog, grab the Dialog-ID from the URL in the detailed view. If something seems off but isn't obviously a bug, mark it as an “Observation.” We'll review these later. Log those observations and bugs as you go – it keeps things organized.
Test Script
Case A: Logging In
First up, log in to the Arbeitsflate at https://af.tt.altinn.no/. This is a crucial first step, guys, because if we can't log in, nothing else matters! Make sure you can access the site without any hiccups. Note any issues you encounter during this initial login attempt. We want to ensure the login process is smooth and straightforward for all users. Successfully logging in means you can move on to the next stage. If you have problems, detail the error messages or any unexpected behavior.
Case B: Navigating the System
Now that we're in, let’s talk navigation. Find your assignors and check your personal “Inbox.” After that, take a peek into one of your assignor's inboxes. Then, browse through the other folders: “For You” and “For Your Assignor.” This step is all about getting a feel for the layout and making sure everything's where it should be. Navigation is key to user experience; if it's clunky or confusing, users will get frustrated. Ensure that all folders load quickly and display the correct content. Are the folder names clear and intuitive? Can you easily switch between different inboxes? Any navigation issues should be noted, as they can significantly impact usability.
Case C: Searching and Filtering
In this case, we're diving into search and filter functionalities. First, do a search to pull up your second newest dialog in your inbox. Once you've got that, clear the search. Next, filter the view to show everything received from “Testdepartement.” Then, expand the filter to limit the selection to the last month, and save the filter. Give your filter a unique name. Create another search (your choice!), and finally, delete the first uniquely named search you made. This case tests the flexibility and robustness of our search and filter tools. Can you easily narrow down your dialog list using various criteria? Does saving and deleting filters work as expected? The ability to quickly find specific dialogs is essential for efficient workflow, so any issues here are critical.
Case D: Dialogs Without Transmissions
Here's where it gets a little special. You've got a Testdialog called “(Spesial) Testdialog med mulighet for manuell setting av status.” This one lets you change its status via buttons in the detailed view. Your mission? Change the status using the buttons and check that it shows up in the expected folder in the list view. Do this for a few different statuses. This test checks how status changes propagate through the system and if they're reflected correctly in the UI. It's important to verify that dialogs appear in the correct folders based on their status, as this helps users keep track of their tasks. Note if status updates are immediate and if the list view accurately reflects these changes.
Case E: Dialogs with Transmissions
Next up, we're dealing with dialogs that have transmissions. You've got two of these. Open the detailed view, but only expand one transmission (for each dialog) before heading back to the list view to see what's what. Then, go back to the detailed view and expand the remaining transmissions before returning to the list view again. This tests how transmissions load and if expanding them affects performance or display in the list view. We need to make sure that users can efficiently manage dialogs with multiple transmissions without experiencing delays or visual glitches. Pay attention to load times and how the interface handles expanding and collapsing transmissions.
Case F: Message Dialogs
Let's find that message dialog (a correspondence) from ???. Your task is to do whatever it takes to make that “det gjenstår mer å se“ (there's more to see) marker disappear. Remember, there was a logic change on June 26th, so don't dig too deep into anything older than that. This tests user interaction and how the system tracks viewed messages. Can you easily clear the