Category: QA Department

  • Webflow Projects

    General Information (Intro)

    Webflow is a website builder that provides ready-to-use blocks, making the assembly process simple and intuitive. With its tools, we can create online stores, landing pages, portfolios, or other types of projects.

    Although Webflow is a no-code platform, it also offers advanced features for developers. Suggested front-end settings ensure that pages are automatically optimized for different devices.

    Testing Webflow projects involves verifying the functionality, responsiveness, and performance of the website. The focus is on ensuring proper display across different devices and browsers, checking interactive elements, measuring page load speed, and confirming that pages match the original design.

    Estimation

    • For simple standard projects, testing takes about 10% of the development time.

    • For projects with forms and animations, it is recommended to allocate around 15% of the development time for testing.

    When estimating testing time, clarify whether a perfect pixel check is required. If yes, allocate at least 15% of the development time for testing.


    Usually, Tablet Devices are out of scope, but this should be confirmed with the PM at the start of the project. If tablet testing is required, the estimate should also be 15% of development time.

    Browsers & Devices

    It is not necessary to test on all devices. Currently, most issues occur on macOS and iPhone (Safari).

    Desktop

    Mobile

    Windows 11 + Chrome (the latest version)

    Android (optional)

    MacOS Tahoe + Safari (the latest version)

    MacOS Sequoia + Chrome (the latest version)

    iPhone + Safari

    iPhone + Chrome

    The latest and previous version of iOS

    Important Notes and Remarks

    Performance and Optimization

    Always pay attention to site performance. All images must be optimized:

    • high quality, no pixelation.

    • Ideally, the size shouldn't exceed 200 KB; (Slightly larger sizes are acceptable if image quality is too poor).

    image-20250925-143402.png
    • lazyload is recommended.

    Reusable Blocks

    If reusable blocks on different pages in Figma Design vary in color shades, font sizes, or spacing, follow the first version. Notify the PM and discuss with the developer.

    Questions

    If you have any questions, contact the developer or the QA Lead. If needed, you may also consult with Alec Shpigar

    https://www.browserstack.com/

    CREDENTIALS

    Login: alex.l@cheitgroup.com

    Password: oZTPxqA69rqiBTvqFEvU

    To perform a perfect pixel check, I recommend using the following extension: PerfectPixel by WellDoneCode.

    To get the same layout as in the design, you can use the Responsive option in DevTools. Alternatively, you can add a custom device with your preferred name to the device list.

    image-20250925-144347.png

  • Reminders Testing

    It’s necessary to check reminders on support projects for preventive purposes monthly.
    You can find the verification list below based on sample One-Line websites: play2win and chiidaspa.
    It describes the WP configurations of Lucky Wheel & Bookly Appointment plugins, and required functionality tests

    • Please, create a Google Sheet with attachments for monitoring the test results and share it with your PM

    • Note that testing should be provided on each locale of the multilingual website

    Bookly Appointment → Notifications&Reminders
    Reference website → https://chiidaspa.stage.one-line.ch/

    ID

    Summary

    Description / Test Data

    Status

    Comments /
    JIRA link to the bug

    1

    Verify the settings of the Bookly Plugin in WP Admin

    eg. https://prnt.sc/hBhJ6GO-F8Uz

    NOT EXECUTED

     

    2

    Verify the email/notification templates from WP Admin

    eg. https://prnt.sc/lFrbeiKncleU

    • сorrectness of HTML/text formatting.

    • dynamic tags (client name, date, time, service, etc).

    • the ability to edit the template via the admin.

    • letter on different devices

    PASSED

     

    3

    Verify that the appointment is successfully booked via Admin Panel

    • new booking is created https://prnt.sc/sb9Jbx12Wd57

    • new booking is added to the calendar

    • the confirmation emails are automatically sent to the client and employee

    FAILED

    add here a link to the bug in Jira / Comment

    4

    Check the appointment in Bookly Calendar

    https://prnt.sc/D8RpixHpuKv-
    Correctness of details:

    • date

    • time

    • contact info

    • payment details

    • appointment status

    • etc

    BLOCKED

    add here a link to the bug in Jira / Comment

    5

    Verify that the appointment is successfully edited via Admin Panel (appointment/calendar tabs)

    6

    Verify the Online Booking form submission

    • the form is successfully submitted

    • client is redirected to the Tank You Page (Bookly → Url Settings)

    NOT EXECUTED

    7

    Verify that data is recorded to the DB&WP after the Online Booking form submission

    eg. Appointments table in WP Admin https://prnt.sc/_7_kb1uxcWQH

    NOT EXECUTED

    8

    Verify that the uncompleted appointment email is sent to the client after the Online Booking form submission

    notification that the request has been received and is waiting for approval

    NOT EXECUTED

    9

    Verify that the client receives the confirmation email after approving the appointment via Admin Panel

    NOT EXECUTED

    10

    Verify that the employee receives an email about new appointment after approving it via Admin Panel

    NOT EXECUTED

    11

    Verify that the Online Booking form offers only available time slots

    check the form after reservation and make sure that the used time slot isn’t available for booking

    NOT EXECUTED

    12

    Verify that an email is sent after appointment cancelation

    1. for client https://prnt.sc/xvY9voFOmZXJ

    2. for employee https://prnt.sc/DXhXq9t9vtji

    NOT EXECUTED

    13

    Verify that an email is sent after appointment rejection

    1. for client https://prnt.sc/Rvi9uEEitHlo

    2. for employee https://prnt.sc/rkP7JVyY23Ct

    NOT EXECUTED

    14

    Verify that reminder of upcoming appointment is sent to employee and client

    Precondition: WP Admin → Bookly → Notifications

    • reminders are enabled

    • sending time is set (eg. 2 hours before event)

    To check the reminder functionality:

    1. modify required records in BD (eg. appointment date&time) and run a cron job manually. If it’s possible do it yourself or ask BE Developer

    2. wait when date&time will be reached and check the notification

    NOT EXECUTED

    15

    Verify to which folder of mailbox the letters are added (Primary/Promotion/Spam)

    Make sure that the letters aren’t in Spam (Gmail, Outlook, etc)

    NOT EXECUTED

    16

    Verify that the employee is able to approve/cancel or reject the appointment (if this option is implemented)

    Please, note that it’s not actual for the reference site

    Eg. an email about new pending appointment is sent to the appropriate employee. It includes a link that automatically confirms, declines, or cancels this appointment
    {approve_appointment_url}
    {cancel_appointment_url}
    {cancel_appointment_confirm_url}
    {reject_appointment_url}

    NOT EXECUTED

    17

    Verify that the client is able to approve/cancel the appointment (if this option is imlemented)

    Please, note that it’s not actual for the reference site

    Eg. email notification that confirms/reminds the client about upcoming visit contains approval/cancellation link
    {approve_appointment_url}
    {cancel_appointment_url}

    NOT EXECUTED

    Lucky Wheel → Notifications&Reminders
    Reference website → https://olp.stage.one-line.ch/

    ID

    Summary

    Description / Test Data

    Status

    Comments /
    JIRA link to the bug

    1

    Verify that the settings of the WP Lucky Wheel Plugin correspond the requirements

    https://prnt.sc/E1FDShWWWgdy

    NOT EXECUTED

     

    2

    Verify that the Block with Lucky Wheel matches the design

    PASSED

     

    3

    Verify the availability of required elements of the Block with Lucky Wheel

    Check (Theme Wheel → Form Page setting) https://prnt.sc/7mbOQkqt0wx1

    FAILED

    add here a link to the bug in Jira / Comment

    4

    Verify the functionality of Lucky Wheel

    • it spins by form submission

    • wheel speed

    • wheel spinning duration

    • wheel can be spun once per day for one email address (error page is opened after 2nd try)

    BLOCKED

    add here a link to the bug in Jira / Comment

    5

    Verify the Lucky Wheel form validation and submission

    Please find the testing list here

    6

    Verify the Lose Page

    The page can be triggered after sending the Lucky Wheel form

    Do following checks:

    NOT EXECUTED

    7

    Verify the Win Page

    The page can be triggered after sending the Lucky Wheel form

    Do following checks:

    NOT EXECUTED

    8

    Verify the Already Played Page

    The page is opened after sending form twice

    Do following checks:

    NOT EXECUTED

    9

    Verify the settings of the WP Mail SMTP reminder plugin in admin

    https://prnt.sc/n2nmPR11cCYN

    NOT EXECUTED

    10

    Check that the verification email is sent after winning in Lucky Wheel

    the verification email is sent https://jmp.sh/G2BOxgcc

    Do following checks

    • mailbox folder (Primary/Promotion/Spam). Make sure that the letter isn’t in Spam

    • email template: from whom email is sent to whom; subject; headers; body content; dynamic tags (client name, etc).

    NOT EXECUTED

    11

    Verify that data is recorded to the DB & WP after form submission

    Check fields and records of the Registration table https://prnt.sc/2I_-qoostKUj

    NOT EXECUTED

    12

    Verify that a reminder to confirm participation is sent to the unverified user

    1. Change the submission form date and trigger notification by running a cron job manually. If it’s possible do it yourself or ask BE Developer https://prnt.sc/Kmrbu5iv5iev
      OR

    2. Wait for the date and time to be reached and check the notification. It’s been 48 hours since the email was sent. https://prnt.sc/e67ApvIM7RFQ


    the reminder is sent https://jmp.sh/AqUxEdNK
    Do following checks

    • mailbox folder (Primary/Promotion/Spam). Make sure that the letter isn’t in Spam

    • email template: from whom the email is sent to whom; subject; headers; body content; dynamic tags (client name, etc).

    NOT EXECUTED

    13

    Verify the validation and submission of the Competition Form (1st and 2nd competition stages)

    Please find the testing list here
    https://prnt.sc/tCpC1DU7jkmy

    NOT EXECUTED

    14

    Verify the Thank You Page (1st and 2nd competition stages)

    The page can be triggered after sending the Competition form https://prnt.sc/OGqqCKkKt8cZ

    Do following checks:

    NOT EXECUTED

    15

    Check that the verification email is sent after submission of Competition form (1st and 2nd competition stages)

    the verification email is sent https://jmp.sh/vuq3gmAP

    Do following checks

    • mailbox folder (Primary/Promotion/Spam). Make sure that the letter isn’t in Spam

    • email template: from whom email is sent to whom; subject; headers; body content; dynamic tags (client name, etc).

    NOT EXECUTED

    16

    Verify that data is recorded to the DB & WP after form submission (1st and 2nd competitions stages)

    Check fields and records of Registration table https://jmp.sh/SgtQaq3i

    NOT EXECUTED

    17

    Verify that a reminder to confirm participation is sent to the unverified user (1st and 2nd competition stages)

    1. Change the submission form date and trigger notification by running a cron job manually. If it’s possible do it yourself or ask BE Developer https://prnt.sc/Kmrbu5iv5iev

    OR

    1. Wait for the date and time to be reached and check the notification. It’s been 48 hours since the email was sent.


    the reminder is sent https://jmp.sh/pWAno8tk

    Do the following checks

    • mailbox folder (Primary/Promotion/Spam). Make sure that the letter isn’t in Spam

    • email template: from whom the email is sent to whom; subject; headers; body content; dynamic tags (client name, etc).

    NOT EXECUTED

  • Bug attributes: Priority & Severity

    Priority and Severity are the most important attributes that should be assigned to a bug report while logging it in Jira. They play a vital role in identifying and addressing issues, allowing for efficient bug tracking and fixing. Сorrectly defined Priority and Severity levels help the team go through the release scheduling process and prevent critical issues from being overlooked.

    DEFINITION:

    Priority is an attribute that determines how quickly the defect needs to be fixed based on the importance of the business. (In what order should a developer fix the bug? Should we fix it now, or can it wait? )

    Severity is the degree of impact that a defect has on the functionality of the tested component or system. (How critical the bug is and what is the influence of the defect on the software? )

    Сonclusion: Severity relates more to the technical part and the priority to the organizational one.

    Bug priority classification:

    Priority Level

    Description

    High

    the high-priority defect must be immediately fixed (ASAP). It is assigned to critical issues that negatively affect the functionality or company’s business and should be corrected first.

    Medium

    it’s the standard priority defined by default in the bug-tracking tool. It’s assigned to the bugs less urgent than high-priority defects and can be fixed when the developers have the bandwidth to take them up. Such bugs can be resolved either in the same release or the next.

    Low

    the low priority is assigned to the bugs that don’t affect the functionality. They are fixed last when there is time and resources for it.

    Bug severity classification:

    Severity Level

    Description

    Samples

    Blocker

    The system cannot be used. Critical failure that completely blocks test execution or project/part of the project at all.

    • It’s impossible to add products to the cart

    • It’s impossible to proceed to the checkout flow

    • Mini-cart disappears, cart page isn’t opened

    • The user isn’t able to pass the login with valid credentials

    Critical

    A significant functional defect that prevents finalizing the testing procedure. It indicates that important functionality fails, but there are workarounds.

    • Accordions aren’t expanded

    • Wrong validation behavior is applied to the input fields

    • An error occurs when the user adds a product to the cart from the Wishlist

    Major

    A substantial bug that impacts functionality and requires urgent attention.

    • Wrong displaying of alternative images carousel

    • Navigation arrows don’t work for the carousel on mobile

    • There is no field validation (in case it’s required)

    Minor

    Indicates an issue that doesn’t affect core functionality. A minor impact that doesn’t break the business logic. (user interface problem).

    • Incorrect font size/type is used for content

    Trivial

    An aesthetic or minor bug that doesn’t affect usability.

    • Minor glitches

    • Typos in the text

    The Severity and Priority Examples

    High Severity & High Priority

    • Server error occurs when a user tries to access the main page

    • The “Login” button of the login form isn’t clickable, after specifying user credentials

    From the technical perspective: the functionality doesn’t work and the website is partially unavailable – Blocker Severity Level

    From a business perspective: users will avoid websites on which not all functions are available to them. Businesses will be impacted.

    Low Severity & High Priority

    • The buttons of the Hero Banner overlap each other. But they are clickable and redirect to the appropriate page.

    • The company logo has a spelling mistake on the homepage.

    From the technical perspective: functionality works, but the user experience isn’t good

    From a business perspective: it’s a drawback from the reputation point

    High Severity & Low Priority

    • The main page of the site is rendered in wrong by old browsers. (overlapped text, empty carousel tiles, the logo isn’t loaded, page layout is broken).

    • Clicking the link in one of the blog articles triggers the Server Error.

    From a technical perspective: It affects the proper website functioning and user navigation on the site or even down the server (2nd sample)

    From a business perspective: The browser version is outdated and the percentage of visitors is low OR the link is on a deep page and a small percentage of users click on it.

    Low Severity vs Low Priority

    • The margins and padding of some components don’t correspond to the design.

    • Spelling issues in paragraph (not on the cover page, heading, title).

    Trivial issue from both: technical and business perspectives.

    Please, find the common issues list with already defined severity levels in Google Sheets. You can refer to it during bug creation.

  • Checklist for the WP admin

    Summary

    Description

    Status

    Comments

    1

    Check the interface for clarity and convenience

    Check:

    • section names

    • displaying

    NOT EXECUTED

    2

    Check the correctness of the login with the correct username and password

    Valid login and password

    PASSED

    3

    Check access to different sections of the admin panel

    Depending on the user role
    – admin
    – editor
    – author
    – user

    FAILED

    4

    Check the creation of a new user in the admin panel after filling out the registration form on the site

    – Check the ability to change the "Roles" for a user in the WP admin
    – Check if user data is saved in the WP admin after registration
    – Check the possibility of changing the user’s e-mail, name, personal data in the admin panel

    5

    Check the correctness of the interface translation into different languages

    If provided
    – EN
    – DE
    – FR
    – etc.

    6

    Check the correct display and operation at different screen resolutions

    Desktop:
    – 2560px
    – 1920px
    – 1440px

    7

    Check WP admin in different browsers

    Browsers:
    – Chrome
    – Safari
    – Opera
    – Firefox
    – Edge

    8

    Check errors in the console in Incognito mode

    There should be no mistakes

    9

    Check create, edit, delete "posts", "pages", "blocks”

    – Check the uniqueness and unambiguity of page/post/block titles
    – Change of text,
    – Change of images
    – Change of styles
    – Move blocks around the page
    – Duplication
    – Copying
    – Delete
    – Turn ON/OFF blocks/sections
    – Remove image for slider/carousel

    10

    Check create, edit, delete "fields”

    – Check the uniqueness and unambiguity of page/post/block titles
    – Text formatting (fonts, colors, lists, links)
    – Switch between editing modes (visual, text)
    – Check the field for validation (empty, field, characters, numbers, Cyrillic)
    – Check fields for validation messages (character length, other file type)
    – Copying
    – Delete

    11

    Check the files you are uploading

    – Check for file type – images, video, audio
    – Check for file size (min/max)
    – Check for uploading from a computer, video, etc.
    – Check for formats *pdf /jpeg/ mp4/ mp3/ avi…
    – Check for the number of files

    12

    Check adding buttons

    – Buttons must be added

    13

    Check adding links

    – Links must be added

    14

    Check for the correct display of changes on the site after the update in the WP admin

    – Save changes in WP and check the site

    15

    Check the site logo in the admin panel

    Possibilities to
    – add
    – remove
    – change

    16

    Check the editing of the favicon in the site admin

    Possibilities to
    – add
    – remove
    – change

    17

    Check the deletion of the "CHE-IT Group" theme from the admin(Appirance->Themes), when starting live (only for Oneline and Rifmedia)

    – Check so that there is no reminder of CHE-IT Group anywhere

    18

    Delete test users/data before go-live

    Check status changes for pages/posts/products

    Status should be
    – draft
    – published
    – private

    Check the display of the page in "Preview" mode

    – The page should not have a broken layout

    Check the linking of each button on the site

    – Buttons have a specific link (not #)

    Check category changes for products/records

    Check
    – add
    – edit
    – delete

  • Checklist for the forms

    ID

    Summary

    Description / Test Data

    Status

    Comments /
    JIRA link to the bug

    F-1

    Verify that the form is according to the design

    Do the following checks:

    • text fonts and styling

    • margins and paddings

    • colors

    NOT EXECUTED

    F-2

    Verify that the displaying of the form is adapted to different screen resolutions/browsers

    Check it across the approved device list

    PASSED

    F-3

    Verify that the form contains all required elements

    https://prnt.sc/BGQMInl4LMeQ

    Example:

    • form title

    • text description

    • fields: mandatory & optional

    • selectors (drop-down list)

    • T&C checkbox

    • Submit/Send button

    FAILED

    F-4

    Verify the action of the "Next"/"Previous" button of the multi-step form

    BLOCKED

    F-5

    Verify the functionality of the checkbox

    the user is able to mark/unmark the checkbox

    NOT EXECUTED

    F-6

    Verify that it’s possible to select/change any value from drop-down

    NOT EXECUTED

    F-7

    Verify that all mandatory fields are marked by asterisks

    NOT EXECUTED

    F-8

    Verify the disappearance of placeholder after clicking/filling in the field

    NOT EXECUTED

    F-9

    Verify styling of specified data in the form

    Do the following checks for manually entered/prefilled data

    • font-family

    • font-size

    • font-color

    • letter-spacing

    • etc

    NOT EXECUTED

    F-10

    Verify the form submission with valid data

    • The form is sent (200 status code in Network tab)

    • The success "Thank you for your message. It has been sent." message is shown https://prnt.sc/hdEGvIRgjCEf

    NOT EXECUTED

    F-11

    Verify the uploading of the attachments to form

    • file types: images, video, audio

    • supported/not supported formats: *pdf /jpeg/ mp4/ mp3/ avi…

    • min/max size

    • uploading of several files (size exceeding)

    • uploading files from a computer and making the real-time photo

    NOT EXECUTED

    F-12

    Verify that form fields are under validation (client side)

    • empty mandatory field is highlighted in red and (eg. "Please fill out this field") error is shown below it

    • field with invalid format data are highlighted in red and (eg. "Please enter a valid e-mail address/phone number/name/zip code"). error is shown below it

    Test Data

    • email without @: oavtest01gmail.com

    • email with several @: oavtest01@@gmail.com

    • email with missing/invalid domain part: oavtest01@gmail. or oavtest01@gmail_.com___

    • exceeded length / too short input (any text field or phone number)

    • only spaces

    • only digits/special symbols instead of name

    • letters in the phone number field

    • wrong format of the date

    • etc

    NOT EXECUTED

    F-13

    Verify error handling after form submission (server response)

    eg. WordPress Integration (Form 7)
    https://prnt.sc/v4NPQOYXm-e9
    https://prnt.sc/hzRitErCDpVz

    NOT EXECUTED

    F-14

    Verify that the user is redirected to the appropriate page after form submission

    Thank You Page: eg. https://prnt.sc/MM9NDQLloVwp

    NOT EXECUTED

    F-15

    Check that a confirmation email/verification email is sent to the user after form submission

    NOT EXECUTED

    F-16

    Verify the template of the received letter and check the availability of the required elements due to configs

    eg. https://prnt.sc/gLY2feSSfHbb

    • From whom email is sent to whom

    • Subject

    • Additional Headers

    • Message Body

    NOT EXECUTED

    F-17

    Verify to which folder of mailbox the letter is added (Primary/Promotion/Spam)

    Make sure that the letter isn’t in Spam

    NOT EXECUTED

    F-18

    Verify that data is recorded to the DB/WP after form submission

    NOT EXECUTED

    F-19

    Verify that the form is successfully cleared

    • The "refill" event is triggered after form submission

    • resetting the specified data by page refreshing / Ctrl+F5

    NOT EXECUTED

    F-20

    Verify that the form and success/error messages are localizable (multi-language website)

    Everything is translated after language-switching

    NOT EXECUTED

    F-21

    Verify the form submission with/without passed reCaptcha

    Make sure that reCaptcha integration is implemented https://prnt.sc/kA_DgWURsuaa

    NOT EXECUTED

    F-22

    Verify the showing of loader/spinner after form submission

    NOT EXECUTED

  • Rief Media Checklist

    Checklist Sample

    Analyze the site and all existing requirements. To optimize verification time, define reusable components on different pages. Based on the design or the current website state, write a testing checklist or use this one(синяя звезда)

    ID

    Summary

    Description / Test Data

    Status

    Comments /
    JIRA link to the bug

    RM-1

    Verify the page layout on different screen resolutions/browsers

    Check it across the approved device list

    NOT EXECUTED

    RM-2

    Verify that the page content is added according to the assets/design

    PASSED

    RM-3

    Verify that the text fonts and styling match the design

    FAILED

    RM-4

    Check the margins and paddings of each component on the webpage

    BLOCKED

    RM-5

    Verify that the hover effect is applied on desktop version

    check the following items:

    • links

    • CTAs

    • navigation buttons

    • icons

    NOT EXECUTED

    RM-6

    Verify that the animation is added according to the requirements

    • content: text and images (scroll animation)

    • sliders

    • background images

    NOT EXECUTED

    RM-7

    Verify the functionality of the content carousels

    • swapping on mobile

    • switching tiles by clicking the navigation arrow buttons on both mobile&desktop versions

    • dot navigation

    • automatic switching of tiles by time

    NOT EXECUTED

    RM-8

    Verify functionality of accordions

    • the accordion is expanded by click

    • the accordion is collapsed by double-click

    NOT EXECUTED

    RM-9

    Verify the actions of buttons

    • redirect to another page

    • scroll to the section of the page (anchor)

    • form submission

    NOT EXECUTED

    RM-10

    Verify the form validation and submission

    Please find the testing list here

    NOT EXECUTED

    RM-11

    Verify that the destination URL is set up for each link on the webpage

    Make sure that there are no anchor # links

    NOT EXECUTED

    RM-12

    Make sure that there are no errors in the console

    NOT EXECUTED

    RM-13

    Verify the video/image quality

    NOT EXECUTED

    RM-14

    Check the Performance of webpage

    • load time (<3 sec)

    • TTFB value (time to 1st byte)

    • lazy load applying

    • video/image optimization

    • etc

    You can use Dev Tools (Performance & Lighthouse tabs) and any testing tool eg. JMeter

    NOT EXECUTED

    RM-15

    Check SEO of webpage

    • no missing or duplicate meta titles/descriptions

    • images with alt tags

    • optimal length of metadata (title/description/alt tag)

    • hreflang tags for multilingual sites

    • no broken internal or external links on page

    You can use the following extensions: Link Checker, Image Alt Text Viewer, SEO META in 1 CLICK

    NOT EXECUTED

    List of browsers/devices

    By default, the testing should be provided on the following devices (BrowserStack can be used):

    • Windows + Chrome (the latest)

    • macOS + Safari (the latest)

    • iOS + Safari (the latest)

    • Android + Chrome (the latest)

    Test Report

    Please, use the document template to report the verification result

    https://docs.google.com/spreadsheets/d/1ftGhm9jgCRYmWY_dI8bGv-eiFsfAnGbi1wclxa4GHS4/edit?usp=sharing

  • Estimation basic

    Estimation_basic.xlsx

    (синяя звезда) IMPORTANT!

    Testing estimation time MUST be 20-25 % of development time (FE + BE).