@mcpher/gas-fakes 1.0.6 → 1.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -28,7 +28,11 @@ You don't have access to the GAS maintained cloud project, so you'll need to cre
28
28
 
29
29
  ### Testing
30
30
 
31
- I recommend you use the test project included in the repo to make sure all is set up correctly. It uses a Fake DriveApp service to excercise Auth etc. Just change the fixtures to values present in your own Drive, then `npm i && npm test`. Note that I use a [unit tester](https://ramblings.mcpher.com/apps-script-test-runner-library-ported-to-node/) that runs in both GAS and Node, so the exact same tests will run in both environments. There are some example tests in the repo. Each test has been proved on both Node and GAS. There's also a shell (togas.sh) which will use clasp to push the test code to Apps Script.
31
+ I recommend you use the test project included in the repo to make sure all is set up correctly. It uses a Fake DriveApp service to excercise Auth etc. Just change the fixtures in .env_template in your own environments, then `npm i && npm test`.
32
+
33
+ Note that I use a [unit tester](https://ramblings.mcpher.com/apps-script-test-runner-library-ported-to-node/) that runs in both GAS and Node, so the exact same tests will run in both environments. There are some example tests in the repo. Each test has been proved on both Node and GAS. There's also a shell (togas.sh) which will use clasp to push the test code to Apps Script.
34
+
35
+ Each test can be run indivually (for example `npm run testdrive`) or all with `npm test`
32
36
 
33
37
  ### Settings
34
38
 
@@ -168,13 +172,14 @@ This was a little problematic to sequence, but I wanted to make sure that any GA
168
172
 
169
173
  Only a subset of methods are currently available for some of them - the rest are work in progress. My approach is to start with a little bit of each service to prove feasibility and provide a base to build on.
170
174
 
171
- v1.0.5
175
+ v1.0.7
172
176
 
173
177
  - `DriveApp` - 50%
174
178
  - `ScriptApp` - almost all
175
179
  - `UrlFetchApp` - 80%
176
- - `Utilities` - 60%
177
- - `Sheets` - `minimal`
180
+ - `Utilities` - almost all
181
+ - `Sheets` - 25%
182
+ - `SpreadsheetApp` - 25%
178
183
  - `CacheService` - 80%
179
184
  - `PropertiesService` - 80%
180
185
  - `Session` - almost all