Содержание
- How to write test cases in excel sheet, test case example
- How to write test cases in excel sheet example
- What is Test case?
- Following standard Test Case Parameters as:
- Before proceeding to writing test case in excel sheet example we will see some Test Case parameters:
- Following sections are displayed as: Home Content search Document Search Calendar User Profile Help
- Test case Management
- Test cases for login page:
- Test Plan template:
- TABLE OF CONTENTS
- Testing Life cycle:
- Following the sequences of Software testing life cycle:
- Test Scenario:
- Test scenario template:
- How to write test scenarios:
- Verify the user successfully login to the application.
- Test Case Example:
- Test cases for pen:
- Test cases Template
- How to write test cases using tools
- Writing test cases
- Types of Test cases
- Functional Testing
- User Interface Testing
- Performance Testing
- Conclusion of article:
- 2 thoughts on “How to write test cases in excel sheet, test case example”
How to write test cases in excel sheet, test case example
The article about How to write test cases in excel sheet. This article complete written based on practical industry experiences. It will help you to crack your interviews.Moreover, we will also cover topics like test case template, test case example (test cases for pen), test plan template, test scenario (test scenario template), testing life cycle and related topics so that you get thorough knowledge in this article. We will proceed step by step so keep patience till end.
We will begin with procedure of writing test case in excel sheet. This is first test case example where we will begin with basics.
How to write test cases in excel sheet example
Before sharing practical experiences of test case example, You can read some basic definition and standard parameters of the Test Cases. We will also focus on test case template after covering basic definitions of these terms.
What is Test case?
A test case is a document, which contain set of test data, prerequisite, Action, expected results and post conditions, developed for a particular test case scenario to verify compliance against a specific functionality requirement.
Test Case act as the starting point for the test execution, and after providing set of input values or test data, the application has a final outcome and leave the system at some end point or also known as execution post condition.
We will need to know standard test case parameters to write test case in excel sheet. Along with knowing the definition of test case, you also must be aware of test scenario template, testing life cycle which is explained further in this article.
Following standard Test Case Parameters as:
Test Case Description
Valid and invalid Test Data
Status – Pass or Fail
Let’s I am going to share with you practical industry experiences. It will help you additionally in writing a test case. Test case examples especially test cases for pen will clear much concepts.
In the organization regularly or practically we are using test case execution tools like Quality Centre, Microsoft Test Manager (MTM) to write a test cases. Each tool has define their own test case template structure.
Like I work with Microsoft Test Manager (MTM) and writing the test cases in following way.
Before proceeding to writing test case in excel sheet example we will see some Test Case parameters:
Following sections are displayed as: Home Content search Document Search Calendar User Profile Help
| Scenario Description : User successfully login to application by using valid credentials | ||
| No | Action | Expected Result |
| 1 | Login Screen: Log in to ABC application using valid user. User ID: admin and Password: admin | Home screen is displayed |
| 2 | Home Screen: Verify the following sections are displayed Home Content search Document Search Calendar User Profile Help | |
| 3 | Home Screen: Click on “User Profile” tab section and Verify the “User Profile” page is displayed | User Profile screen is displayed |
| 4 | User Profile Screen: Verify the default User details are displayed including User ID and Passwords | User details are displayed including User ID and Passwords |
| 5 | User Profile Screen: Enter the User registration date and click on “Save” button | User Profile Screen successfully updated with specified registration date. |
Always maintain the valid and invalid test data with you. Because, while preparing test execution report you should provide set of all executed test data.
Above information were primary article about “How to write test cases in excel sheet example”. I have explained exact procedure of writing a test cases in excel sheet which was test case example. On your request, we have also covered “Test case for login page“, “test cases for pen“, “How to write test scenarios” and basic definition and overview of related terms like test scenario, testing life cycle, test case templates.
Let us first begin with Test case management before proceeding to other test case examples or test plan template. Initially we need to identify test case management tools and lots of pre-requisites to initiate testing process such as Test case management.
Test case Management
Now by using Test case management tools, it is simple to manage all testing process, also following tools are available to maintain all process like test case scenario, test case template, test plan template and how to write test cases etc.
- Test Lab
- QTest
- Test Link
- Quality center
- PractiTest
- TFS
Test cases for login page:
Now, we will begin with most awaited test cases for login page. After tis we will also explain ‘test cases for pen‘ so that you get more clearity. We usually write test cases for login page for every application. Almost every login page should have the following fields:
Email/Phone Number/Username’ – Textbox
Remember Me – Checkbox
Keep Me Signed In- Checkbox
Forgot Password- Link
Sign up/Create an account-button
There are lots of test cases examples, test scenario, test plan templates which are available specially on Test cases for login page and same I will be mentioned in my upcoming article.
We will also be focusing on test case example for manual testing and test case example for web application.
Test Plan template:
After completing the test case for login page, now lets focus on Test Plan Template. Test Plan is use for to decide common strategy that will be applied across the testing an application. Test plan template is one of the important points of this article.
(Name of the Product)
(Names of Preparers)
TABLE OF CONTENTS
2.0 OBJECTIVES AND TASKS
4.0 Testing Strategy
4.1 Alpha Testing (Unit Testing)
4.2 System and Integration Testing
4.3 Performance and Stress Testing
4.4 User Acceptance Testing
4.5 Batch Testing
4.6 Automated Regression Testing
4.7 Beta Testing
5.0 Hardware Requirements
6.0 Environment Requirements
7.0 Test Schedule
8.0 Control Procedures
9.0 Features to Be Tested
10.0 Features Not to Be Tested
11.0 Resources/Roles & Responsibilities
13.0 Significantly Impacted Departments (SIDs)
Test plan template was explained in a detailed manner so that no part of test case template and test plan template were left untouched. No let us see testing life cycle.
Testing Life cycle:
Software Testing Life Cycle refers to testing process which has specific steps to be executed in a definite sequence to ensure that the quality goals have been met. In STLC process, each activity is carried out in a planned and systematic way. Each phase has different goals and deliverables. Let us focus on each and every aspect of Testing Life Cycle in detail.
Following the sequences of Software testing life cycle:
- Requirement Analysis
- Test Planning
- Test case design
- Test case execution
- Test case cycle end
Sequence of Testing life cycle must be maintained as given above. If you have any doubts regarding testing life cycle, you can ask in the comment section below.
Test Scenario:
Here begins other important point, that is, testing scenario where we will cover test scenario template, how to write test scenarios and test case template xls. Let me describe in detail, while creating a test scenario, at first need to mention Test scenario id in sequentially. Specify the referred document names for future purpose also write test scenario description like what and how need to test the functionality. Provide the importance to test scenario like High, Medium or low etc.
Mention the number of test cases which are created based on the same scenario. I am giving the particle example to easily understand. Now we will focus in detail on test scenario template.
Test scenario template:
Test scenario is the pre-requisite of the test cases. That is the reason why we have added test scenario template in test case example article. The various type of test scenario template is used in industry. I am going to provide very simple test scenario template to get more clarity.
We need to refer excel to mentioned following points such as:
- Test Scenario ID
- Requirement Reference document
- Test Scenario description
- Importance – in other words priority
- of Test Cases
We have given basics of test Scenario, then test case template. Now let us focus on how to write test scenarios or procedure in writing test scenarios.
How to write test scenarios:
Here I am providing one example for how to write test scenario on login page. Assuming that we have created all columns in a excel.
Test Scenario id – 1
Requirement Reference document – Login to application (xxxx)
Test scenario description –
To login application successfully with valid credentials
Provide valid user name in the User Name text box
Provide valid Password in the Password text box
Verify the user successfully login to the application.
Importance– High
No of Test cases – 1
“Writing test scenario” is a practical thing for which you need to have your concepts clear regarding test scenario which is explained above.
Test Case Example:
Here comes the test case example. We have seen ‘how to write a test case in excel sheet‘ in detail, then test case for login page. Lets see on more test cases for pen.
Test Case Description – Verify the successful login with valid user
Actual Results – Provide valid user details with password
Expected – User successfully logged in to Application
Test Data – User Name and Password
Test cases for pen:
Before creating the test cases for pen, we need to think about what exactly the product requirement. Explore the more ideas about same product. Now basically we are looking test cases on pen.
There are some pre-requisites to write test cases for pen is, pen must have a refill and refill must have ink.
- Verify the user is able to hold the pen comfortably
- Verify the user is able to write smoothly
- Verify the ink flow, It should not overflow
- Verify the pen material quality is good not to hard
- Verify the brand name or company name should be mentioned on the pen
- Verify the other refills fits or not in the same pen.
- Verify the user can write on any type paper like smooth, rough, thick, thin, glossy etc.
- Verify the pen cap is opened smoothly
- Verify the pen gripper is verify smooth
- Verify the color of the ink like black, blue, green.
We have almost covered major sections of test case template, test plan template excel and also how to write test cases.
Test cases Template
Test Case template is varying to company to company, as all companies are using different test case templates, here i have mentioned standard template
- No
- Test Case description
- Actual result
- Expected Result
- Test Data
We can write an test cases in excel as well as in Test management tools like, JIRA, qtest, MTM and they are following the similar format for test case writing.
Writing test cases
The main goal is writing test cases define “what” and “how”. It is part of process in the test strategy.
Both knowledge and experience is required for writing test cases.
Types of Test cases
There are different types of test cases, functional test cases, user interface test cases in short UI test cases, performance test cases, integration test cases, usability test cases, database test cases, User Acceptance test cases.
I will explain some important testing type in short and remaining are described in my other articles.
Functional Testing
In simple terms, Functional Testing is a type of software testing whereby the system is tested against the functional requirements/specifications. Functions (or features) are tested by feeding them input and examining the output. Functional testing ensures that the requirements are properly satisfied by the application.
User Interface Testing
User interface testing, a testing technique used to identify the presence of defects is a product/software under test by using Graphical
Performance Testing
Performance Testing is defined as a type of testing to ensure applications will perform well under their expected workload.
Conclusion of article:
In this detailed article, I have given how to write test cases in excel with example. Also I have given the test cases for login page and test cases for pen for more clarity about this topic. Theory concepts of each practical application was also provided. Test plan template, test case template, test case example, test scenario and testing life cycle were some of the highlights of this article.
If you have any doubts, feel free to ask in comment section. I will answer them all.
2 thoughts on “How to write test cases in excel sheet, test case example”
The testing performed in order to learn each function of the application and explore it is known as exploratory testing. It is applied when requirement document is not available or insufficient details are provided.
ex: To explore new features of a mobile phone without reading instruction manual.
Источник
What is Test Case Template?
A Test Case Template is a well-designed document for developing and better understanding of the test case data for a particular test case scenario. A good Test Case template maintains test artifact consistency for the test team and makes it easy for all stakeholders to understand the test cases. Writing test case in a standard format lessen the test effort and the error rate. Test cases format are more desirable in case if you are reviewing test case from experts.
The template chosen for your project depends on your test policy. Many organizations create test cases in Microsoft Excel while some in Microsoft Word. Some even use test management tools like HP ALM to document their test cases.
Click Below to download Test Case XLS
Download Test Case Template(.xls)
Irrespective of the test case documentation method chosen, any good test case template must have the following fields
| Test Case Field | Description |
|---|---|
| Test case ID: | Each test case should be represented by a unique ID. To indicate test types follow some convention like “TC_UI_1” indicating “User Interface Test Case#1.” |
| Test Priority: | It is useful while executing the test.
|
| Name of the Module: | Determine the name of the main module or sub-module being tested |
| Test Designed by: | Tester’s Name |
| Date of test designed: | Date when test was designed |
| Test Executed by: | Who executed the test- tester |
| Date of the Test Execution: | Date when test needs to be executed |
| Name or Test Title: | Title of the test case |
| Description/Summary of Test: | Determine the summary or test purpose in brief |
| Pre-condition: | Any requirement that needs to be done before execution of this test case. To execute this test case list all pre-conditions |
| Dependencies: | Determine any dependencies on test requirements or other test cases |
| Test Steps: | Mention all the test steps in detail and write in the order in which it requires to be executed. While writing test steps ensure that you provide as much detail as you can |
| Test Data: | Use of test data as an input for the test case. Deliver different data sets with precise values to be used as an input |
| Expected Results: | Mention the expected result including error or message that should appear on screen |
| Post-Condition: | What would be the state of the system after running the test case? |
| Actual Result: | After test execution, actual test result should be filled |
| Status (Fail/Pass): | Mark this field as failed, if actual result is not as per the estimated result |
| Notes: | If there are some special condition which is left in above field |
Optionally you can have the following fields depending on the project requirements
- Link / Defect ID: Include the link for Defect or determine the defect number if test status is fail
- Keywords / Test Type: To determine tests based on test types this field can be used. Eg: Usability, functional, business rules, etc.
- Requirements: Requirements for which this test case is being written
- References / Attachments: It is useful for complicated test scenarios, give the actual path of the document or diagram
- Automation ( Yes/No): To track automation status when test cases are automated
-
Custom Fields: Fields particular your project being tested due to client/project requirements.
Click below to download Test Case Excel File
Download the above Test Case Template(.xls)
Click below to download Test Case Word File
Download the above Test Case Template(.docx)
Hello friends! In this post we will present a test case template in excel/spreadsheet, describing the use of each field in detail.
Ideally, a test case management tool should be used for managing the test cases and test execution cycles. But for smaller projects, many organizations still prefer to use spreadsheets for avoiding the overhead of maintaining and configuring a tool.
So, let’s begin.
What is a Test Case?
A Test Case is a document containing a series of actions executed to verify the different features of an application. A test case has fields like test steps, test data, preconditions, expected results, actual result, test execution status, etc. A tester executes these test cases and marks them as pass and fail.
What is Test Case template?
Most organizations want to maintain uniformity across different projects, be it during the development phase or the testing phase.
In order to follow a uniform testing process, a test case template is defined which is nothing but a template that contains the different fields that the test cases should have.
Now, we will see the different fields of a test case – both mandatory as well optional.
TestCaseId
This field uniquely identifies a test case. It is mapped with automation scripts(if any) to keep a track of automation status. The same field can be used for mapping with the test scenarios for generating a traceability matrix. E.g. – GoogleSearch_1
Component/Module
This field specifies the specific component or module that the test case belongs to. E.g. – Search_Bar_Module.
Priority
This field is used to specify the priority of the test case. Normally the conventional followed for specifying the priority is either High, Medium, Low or P0, P1, P2, P3, etc with P0 being the most critical.
Description
In this field describe the test case in brief. E.g. – Verify that when a user writes a search term and presses enter, search results should be displayed.
Pre-requisites
In this field specify the conditions or steps that must be followed before the test steps execution e.g. – “Browser is launched”.
Test Steps
In this field, we mention each and every step for performing the test case. The test steps should be clear and unambiguous e.g.-
- Write the URL – https://google.com in the browser’s URL bar and press enter.
- Once google.com is launched, write the search term – “Apple” in the google search bar.
- Press enter and observe the search results.
Test Data
In this field, we specify the test data used in the test steps. E.g. in the above test step example, we could use the search term-“apple” as test data.
Expected Result
This step marks the expected result after the test step execution. This used to assert the test case. E.g. search results related to ‘apple’ should be displayed.
Actual Result
In this step, we specify the actual result after the test step execution. E.g. – search results with the ‘apple’ keyword were displayed.
Status/Test Result
In this step, we mark the test case as pass or fail based on the expected and actual results. Possible values can be – Pass, Fail, Not executed.
Test Executed by
In this field, we specify the tester’s name who executed the test case and marked the test case as pass or fail.
Apart from these mandatory fields, there are many optional fields that can be added as the organization or application’s need like-
- Automation status – For marking if a test case is automated or not.
- TestScenarioId – For a mapping test case with its test scenario.
- AfterTest step – For specifying any step required to be executed after performing the test case.
- TestType – To specify if the test comes under any specific testing category like regression, sanity, smoke, etc.
Test Case Template Xls Free Download
Now you can download the test case template in Xls format. Along with the template, we have also provided a sample test case for your reference.
This completes our tutorial on the test case template. Feel free to use this template in your project and let me know in the comments if you have any questions.
Kuldeep is the founder and lead author of ArtOfTesting. He is skilled in test automation, performance testing, big data, and CI-CD. He brings his decade of experience to his current role where he is dedicated to educating the QA professionals. You can connect with him on LinkedIn.
What We Are Learn On This Post
Test Cases For Login Page In Excel Sheet Pdf: This post is the continuation of the Manual test case examples series. Here we will discuss all the possible Test Cases For the Login Page In Excel Sheet Pdf.
In your testing carer, you may have got a chance to test any web application which has login functionality. If you have come across such similar functionality, then you got to know that helps to secure your application.
| Post On: | Test Case For Login Page |
| Post Type: | Test Case |
| Published On: | www.softwaretestingo.com |
| Applicable For: | Freshers & Experience |
| Join For Updates | Telegram Group Link |
Those who have valid credentials those peoples can only access the application. So login Page is taken care of a major role in the application. So we are trying to cover all the possible test scenarios. As per the client’s requirement, the condition may change. So in this test case for the login page in the excel sheet post, we are trying to cover some of the common scenarios. The login page not only gives you the authority to change your account but also provides the freedom to see the critical and confidential information behind the login page.
Elements Of a Login Page
Before writing the test scenario for the login page, imagine if you have the mockup screen. The first, try to find all the elements of the page. The Login page may have the following elements on it:
- Email / Username / Password Text Box
- Remember Me CheckBox
- Login Button
- Login via the Facebook button
- Log in via a Twitter button
- Login via the GitHub button
- Login via the Google button
- Login Screen For Different resolution on Mobile, Desktop & Tab.
- If you try to access Your account without login, it should be redirected to the login page.
- Spam users’ accounts are deactivated, and they should not be able to log in.
- CAPTCHA displayed on ten try to log in unsuccessfully
We try to discuss all the possible negative and positive scenarios of the Login page test case with some basic examples if we have missed some basic test scenarios, which can lead to a bad user experience.
So, we came up with a list of scenarios to Test the Login Page, and gradually we will be adding more such checks to this list.
For this scenario, first, let us divide all the possible categories like:
- Basic Field Validations of GUI
- Security Validations
- Testing Captcha
- Session
- Browser
Login Test Cases In Excel – Field Validation On GUI
- Check if the cursor is the focus of the username text box when you open the login page.
- Check whether tab functionality (move the cursor from one text box to another) is working.
- Check the minimum and maximum lengths of the text boxes are defined or not.
- Check whether Password field values are displayed in masked format or not.
- Check whether the validation message is displaying based on the input value.
- Check the valid credential user should be able to log in
- Check if the user is redirected to the forget password page after clicking on the link.
- Check if the user is redirected to the signup page after clicking on signup page.
- Check users should not be able to log in with valid user names and invalid passwords.
- Check user should not be able to log in with an invalid username and valid password.
- Check user should not be able to log in with a blank user field and valid password.
- Check user should not be able to log in with a valid user and blank password field.
- The system should block the IP or User name after frequent unsuccessful (defined invalid login attempts) login.
- Check if the data of all the text boxes are clear after hitting the reset button.
- Check by using the keyboard tab functionality; the user can select the web element through the tab button.
- Check if the user can click on the login button through the enter button or not.
- Check the user credential remained on the field after clicking remember and get back to the login screen again.
- Check if the login screen appears after clicking on a login link or login button.
- Check is all login-related elements and fields are present on the login page.
- Check the alignment of displayed elements on the login screen that should be compatible with cross-browser testing.
- Different elements’ sizes, colors, and UI should match the specifications.
- Check that the application’s login page is responsive and aligns properly on different screen resolutions and devices.
Login Page Test Cases In Excel Captcha
- When a user does not validate the captcha, the user should not be allowed to log in.
- Check whether the link is present so a user can refresh the captcha.
- Check the input field of the captcha is case-sensitive or not.
- There should be an option for audio support, so the audio user can fill in the captcha after playing.
- The angle and background texture of the captcha should be different so that captcha-cracking programs can not break them easily.
Test Cases For Login Page Xls Security Test Scenarios
- XSS scripts should not affect the system, and Users should not be allowed to log in. A proper validation message should be displayed.
- Check if the SSL certificate is implemented in the application or not.
- Users should not be allowed to copy and paste the password from the text boxes.
- Check if a user is logging in from a new device; a notification should be sent to the registered user.
- SSL certificate should be implemented/ installed to secure the platform.
- The password should not be worked when copied.
- The login form should not reveal security information in view page source mode.
- The login form should not be vulnerable to SQL injection.
- Check the password format should be encrypted.
- When a logged-in user copies the URL and pastes it into a new window, it should redirect to the login page.
- Two-way authentication through OTP on mobile/email should be tested for banking applications.
Login Page Test Cases In Excel Session
- Check if a user successfully logs out; if the user clicks, the back button should not take the User to logged-in mode.
- If a user logs in through multiple devices and logs out from one device, then automatically, the user should log out from all the devices.
- Check that session time out an application.
- Maximum Session time should be set for the Secured website.
- If a user clears all the cookies of a browser and tries to go to a specific page of the application, then it should ask for credentials again.
- The browser’s ‘Remember Form Data’ setting should not remember the password.
- Validate the login functionality when browser cookies are turned OFF.
Negative Test Cases For Login Page
- Check if a user can log in with an expired password or not.
- Check if an unverified user can log in to the application or not.
- Check if the login functionality with blank fields
- Check the login functionality with SQL injections
- Check if the login functionality with incorrect email addresses and passwords.
Test Case Template Excel For Login Page – Performance Test
- Check how many users log in to an application at a time
- Check the response time when the user logs in to the application.
- Check when more than expected users login to the application at a time; the application should not be crashed.
Conclusion
If you still try to write the test scenario in an excel format, then you can follow one of our earlier published articles; where do we have to write in detail how to write the test cases in an Excel sheet?
We hope we have covered almost all testing scenarios, but you can comment in the comment section if you find any missed test cases. We will update this Login page test scenario article as per your suggestions.
Reader Interactions
Хороший Пример теста шаблон поддерживает тестовую последовательность артефакта для тестовой команды и делает его легким для всех заинтересованных сторон , чтобы понять тестовые случаи. Написание тестового примера в стандартном формате уменьшает нагрузку на тест и уровень ошибок. Формат тест-кейсов более желателен, если вы просматриваете тест-кейс от экспертов.
Шаблон, выбранный для вашего проекта, зависит от вашей политики тестирования. Многие организации создают контрольные примеры в Microsoft Excel, а некоторые — в Microsoft Word. Некоторые даже используют инструменты управления тестированием, такие как HP ALM, для документирования своих тестовых случаев.
Нажмите ниже, чтобы загрузить Test Case XLS
Скачать шаблон тестового примера (.xls)
Независимо от выбранного метода документации тестового примера, любой хороший шаблон тестового примера должен иметь следующие поля
| Поле теста | Описание |
|---|---|
| Идентификатор тестового примера: |
|
| Приоритет теста: |
|
| Наименование модуля : |
|
| Тест разработан : |
|
| Дата разработки теста : |
|
| Тест выполнен : |
|
| Дата проведения теста : |
|
| Имя или название теста : |
|
| Описание / Краткое содержание теста : |
|
| Предварительное условие : |
|
| Зависимости : |
|
| Тестовые шаги : |
|
| Тестовые данные : |
|
| Ожидаемые результаты : |
|
| Постусловие : |
|
| Фактический результат : |
|
| Статус (Fail / Pass): |
|
| Примечания : |
|
При желании вы можете иметь следующие поля в зависимости от требований проекта
- Ссылка / Дефект ID : Включите ссылку на дефект или определить число дефектов , если статус тестов отказобезо-
- Ключевые слова / тип теста : для определения тестов на основе типов тестов можно использовать это поле. Например: юзабилити, функциональность, бизнес-правила и т. Д.
- Требования : требования, для которых написан этот контрольный пример
- Ссылки / Приложения : Полезно для сложных тестовых сценариев, указывать фактический путь к документу или диаграмме.
- Автоматизация (Да / Нет) : для отслеживания состояния автоматизации, когда тесты автоматизированы
-
Настраиваемые поля : Поля, относящиеся к конкретному тестируемому проекту, в соответствии с требованиями клиента / проекта.
Шаблон тестового примера
Нажмите ниже, чтобы скачать тестовый файл Excel