GroceriStar/groceristar-fetch

Move detailed tests from groceristar project to other projects too

Open

#102 opened on Oct 20, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (16 forks)auto 404
enhancementgood first issuehelp wantedin-progresstests

Repository metrics

Stars
 (8 stars)
PR merge metrics
 (PR metrics pending)

Description

We should have tests, split for sections, related to each separated file. We should have few describes We should have count, checking props, check objects structure inside, maybe count of arrays, inside the props too.

  1. count
  2. props
  3. objects structure
  4. count of arrays inside the props of file too.

Repeate all this stuff for each of project

This is a code that i use for groceristar in order to know how much data we have inside this files:

// module.count = function() {
//
// 	console.log('ingredient ' +  _.size() )
// 	console.log('department ' +  _.size() )
// 	console.log('grocery ' +  _.size() )
// 	console.log('users ' +  _.size() )
// 	console.log('ingredient ' +  _.size() )
//
//
// };

Index Test - should work for anyone file. right now its only for ChickenKyiv

Contributor guide

Research direction
Examine the existing test structure in the groceristar project and understand the patterns for count, props, object structure, and array counting. Then replicate these tests for other projects in the repository. Ensure each test file covers the described aspects.
Tech stack
javascript
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75