Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nam nguyen 08 fd2 #122

Draft
wants to merge 48 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
48 commits
Select commit Hold shift + click to select a range
9ef8a45
Added html sub dir to create a subtab in fd2_school with temporary co…
ngpmnam Sep 17, 2024
8e43941
Created html.html and formatted Harvest Report and My Sample Harvest …
ngpmnam Sep 18, 2024
e904f07
Italicize mock and add breaks and line as indicated in html.html
ngpmnam Sep 18, 2024
8b7f5de
Created button and text field for Harvest Report
ngpmnam Sep 18, 2024
7401b43
Created Crop and Field Drop down lists
ngpmnam Sep 19, 2024
c089c98
Created Start and End Date
ngpmnam Sep 19, 2024
3605d2d
Test
ngpmnam Sep 19, 2024
228ba7a
Created Table for Sample Report
ngpmnam Sep 19, 2024
2821922
Added the second sub-tab
ngpmnam Sep 26, 2024
8edefec
Autmoated Header
ngpmnam Sep 26, 2024
1b0a239
Automated date and crop
ngpmnam Sep 26, 2024
7dc9977
Added Ternary Statement to Header
ngpmnam Sep 26, 2024
0005a35
v-for for cropDropDown and fieldDropDown
ngpmnam Sep 26, 2024
5bbf673
Added v-for to report table
ngpmnam Sep 26, 2024
50af591
Fixed parameters for multiple v-model/v-for that is outside the scope…
ngpmnam Sep 26, 2024
7b9ca7c
Vue.config.devtool = true
ngpmnam Sep 26, 2024
4c04313
Created vue2 subtab and vue2.html
ngpmnam Oct 7, 2024
08be886
Created Generate Report button that generates a specific template of …
ngpmnam Oct 7, 2024
d338db8
Created methods in Vue instance and created a function to handle the …
ngpmnam Oct 7, 2024
869ec28
Add a "Row" column to the report so that each row is numbered
ngpmnam Oct 7, 2024
b58da7b
Hide the table headings if no report is displayed
ngpmnam Oct 7, 2024
5f9e07c
Binded min and max to date selection in previous activities already.
ngpmnam Oct 7, 2024
1864236
Created new branch NamNguyen-05-API
ngpmnam Oct 9, 2024
17e237f
Bind Farm, User, and Language to Vue instance
ngpmnam Oct 9, 2024
b9be31c
Generate Button now loads Farm, User, and Language values on to the page
ngpmnam Oct 9, 2024
153a423
Generate Report now pulls information from API to generate Farm, User…
ngpmnam Oct 9, 2024
7fbbf4d
Retrieved crop names from farm API
ngpmnam Oct 9, 2024
8753e94
Create NamNguyen-06-API2 and added API2 sub-tab
ngpmnam Oct 16, 2024
193caf4
Added a variable that holds pages requested from endpoint
ngpmnam Oct 16, 2024
882fbcb
Changed the GetAllPages function to fit what is asked
ngpmnam Oct 16, 2024
4b405d8
Automated the table by grabbing accurate values from API endpoints
ngpmnam Oct 16, 2024
d724fe2
Finished table report and deleted codes that are no longer useful (fa…
ngpmnam Oct 16, 2024
1d2e855
Report now generates only logs for chosen crop
ngpmnam Oct 16, 2024
f77724b
cypress testing first.spec.js following tutorial
ngpmnam Oct 23, 2024
34dcc43
Added e2e sub-tab
ngpmnam Oct 23, 2024
c92f31f
Cypress test default start and end dates
ngpmnam Oct 23, 2024
e7f92c6
cypress tests for the crop drop down
ngpmnam Oct 23, 2024
9f86e8c
Added tests for actions with generate button
ngpmnam Oct 23, 2024
5456d9d
Continued to write cypress test for the farm, user, and lanugage elem…
ngpmnam Oct 23, 2024
358af63
Created new FD2 sub-tab
ngpmnam Oct 31, 2024
48403fd
Changed crop drop down using DropDownWithAll Component
ngpmnam Oct 31, 2024
13b56d1
Crop drop down now shows all rows for all the crops
ngpmnam Oct 31, 2024
2dbe928
Changed link for cypress tests fd2
ngpmnam Oct 31, 2024
75d2558
Changed Cypress Test fd2.defaults.spec.js to fit fd2 sub-tab
ngpmnam Oct 31, 2024
e104550
Added CustomTableComponent to replace HTML harvest table
ngpmnam Nov 1, 2024
48c011f
Created Cypress Test for Harvest Report Table
ngpmnam Nov 1, 2024
778349a
Added test for harvest report table's headers
ngpmnam Nov 1, 2024
e993fe4
Minor changes with fd2.html file to fix bugs, added tests for the har…
ngpmnam Nov 1, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
143 changes: 143 additions & 0 deletions farmdata2/cypress/e2e/1-getting-started/todo.cy.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,143 @@
/// <reference types="cypress" />

// Welcome to Cypress!
//
// This spec file contains a variety of sample tests
// for a todo list app that are designed to demonstrate
// the power of writing tests in Cypress.
//
// To learn more about how Cypress works and
// what makes it such an awesome testing tool,
// please read our getting started guide:
// https://on.cypress.io/introduction-to-cypress

describe('example to-do app', () => {
beforeEach(() => {
// Cypress starts out with a blank slate for each test
// so we must tell it to visit our website with the `cy.visit()` command.
// Since we want to visit the same URL at the start of all our tests,
// we include it in our beforeEach function so that it runs before each test
cy.visit('https://example.cypress.io/todo')
})

it('displays two todo items by default', () => {
// We use the `cy.get()` command to get all elements that match the selector.
// Then, we use `should` to assert that there are two matched items,
// which are the two default items.
cy.get('.todo-list li').should('have.length', 2)

// We can go even further and check that the default todos each contain
// the correct text. We use the `first` and `last` functions
// to get just the first and last matched elements individually,
// and then perform an assertion with `should`.
cy.get('.todo-list li').first().should('have.text', 'Pay electric bill')
cy.get('.todo-list li').last().should('have.text', 'Walk the dog')
})

it('can add new todo items', () => {
// We'll store our item text in a variable so we can reuse it
const newItem = 'Feed the cat'

// Let's get the input element and use the `type` command to
// input our new list item. After typing the content of our item,
// we need to type the enter key as well in order to submit the input.
// This input has a data-test attribute so we'll use that to select the
// element in accordance with best practices:
// https://on.cypress.io/selecting-elements
cy.get('[data-test=new-todo]').type(`${newItem}{enter}`)

// Now that we've typed our new item, let's check that it actually was added to the list.
// Since it's the newest item, it should exist as the last element in the list.
// In addition, with the two default items, we should have a total of 3 elements in the list.
// Since assertions yield the element that was asserted on,
// we can chain both of these assertions together into a single statement.
cy.get('.todo-list li')
.should('have.length', 3)
.last()
.should('have.text', newItem)
})

it('can check off an item as completed', () => {
// In addition to using the `get` command to get an element by selector,
// we can also use the `contains` command to get an element by its contents.
// However, this will yield the <label>, which is lowest-level element that contains the text.
// In order to check the item, we'll find the <input> element for this <label>
// by traversing up the dom to the parent element. From there, we can `find`
// the child checkbox <input> element and use the `check` command to check it.
cy.contains('Pay electric bill')
.parent()
.find('input[type=checkbox]')
.check()

// Now that we've checked the button, we can go ahead and make sure
// that the list element is now marked as completed.
// Again we'll use `contains` to find the <label> element and then use the `parents` command
// to traverse multiple levels up the dom until we find the corresponding <li> element.
// Once we get that element, we can assert that it has the completed class.
cy.contains('Pay electric bill')
.parents('li')
.should('have.class', 'completed')
})

context('with a checked task', () => {
beforeEach(() => {
// We'll take the command we used above to check off an element
// Since we want to perform multiple tests that start with checking
// one element, we put it in the beforeEach hook
// so that it runs at the start of every test.
cy.contains('Pay electric bill')
.parent()
.find('input[type=checkbox]')
.check()
})

it('can filter for uncompleted tasks', () => {
// We'll click on the "active" button in order to
// display only incomplete items
cy.contains('Active').click()

// After filtering, we can assert that there is only the one
// incomplete item in the list.
cy.get('.todo-list li')
.should('have.length', 1)
.first()
.should('have.text', 'Walk the dog')

// For good measure, let's also assert that the task we checked off
// does not exist on the page.
cy.contains('Pay electric bill').should('not.exist')
})

it('can filter for completed tasks', () => {
// We can perform similar steps as the test above to ensure
// that only completed tasks are shown
cy.contains('Completed').click()

cy.get('.todo-list li')
.should('have.length', 1)
.first()
.should('have.text', 'Pay electric bill')

cy.contains('Walk the dog').should('not.exist')
})

it('can delete all completed tasks', () => {
// First, let's click the "Clear completed" button
// `contains` is actually serving two purposes here.
// First, it's ensuring that the button exists within the dom.
// This button only appears when at least one task is checked
// so this command is implicitly verifying that it does exist.
// Second, it selects the button so we can click it.
cy.contains('Clear completed').click()

// Then we can make sure that there is only one element
// in the list and our element does not exist
cy.get('.todo-list li')
.should('have.length', 1)
.should('not.have.text', 'Pay electric bill')

// Finally, make sure that the clear button no longer exists.
cy.contains('Clear completed').should('not.exist')
})
})
})
Loading