January 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by HernÃ¡n Morales Durand

Hi Guillermo 2018-01-29 6:00 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Sun, Jan 28, 2018 at 8:51 AM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> Hi Stef, >> >> 2018-01-28 4:15 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> > Ok I see. I think that I never tried this version of Pillar on windows. >> > And I hate make because it is impossible for me to debug it. I will >> > check with Damien >> > because I do not get make. >> > >> > Now we removed the dependency to make in the dev branch >> > Could you try the following: >> > https://github.com/pillar-markup/pillar/blob/newpipeline/README.md >> > >> >> Tried both options, 1) downloading pre-compiled and 2) building from >> sources+setting up environment. >> 1) Nothing happened after "pillar archetype build", exit without >> error, no stdout output, no _result folder >> 2) I got confused with this: >> >> mv pillar ~/.pillar >> >> because now I have two directories: the .pillar in HOME and the build/ >> directory separated. And no "pillar" shell script so should I copy the >> one from 1) ? >> I will re-check tomorrow maybe I'm reading this the wrong way. >> > > Ah! the instructions are not right :) Sorry for that. > > Actually, the instructions are written so you execute the build script > from within the pillar repository. Something like this. > > $ git clone git@github.com:pillar-markup/pillar.git -b newpipeline > $ cd pillar > $ ./scripts/build.sh > > > > It will never work because the issue I described above with the magic variable. ./pharo Pharo.image eval --save 'Metacello new baseline: '\''Pillar'\''; repository: '\''filetree:///c/MySmalltalkProjects/Pillar ..... must be ./pharo Pharo.image eval --save 'Metacello new baseline: '\''Pillar'\''; repository: '\''filetree:///c:/MySmalltalkProjects/Pillar .... I don't know how to write it more clearly :) Do you want me to open an issue here? https://github.com/pillar-markup/pillar/issues Cheers, HernÃ¡n > that is why the next lines are > > $ mv pillar ~/.pillar > > > and > > $ export PILLAR_HOME="$HOME/.pillar/build"$ export PATH="$PATH:$PILLAR_HOME" > > > Now, to fix your setup, you can try: > > $ mv build ~/.pillar/ > > and that should make the pillar launcher scripts available. > > We changed these scripts with stef a couple of weeks ago to keep not only > the build directory but also the git repository, and so be able to upgrade > pillar. But a docbug slipped in ^^. > > Can you check it like that? > > >> > so that I can see if this is working. >> > I know that guille worked on windows and AppVeyor support but he got >> > distracted by the github refactoring. >> > We hope to come back this week to Pillar. We plan to release a version >> > (still with Magritte) but with a full documentation. >> > >> >> Cool, I will test because I have several chapters ready to publish. >> >> > Stef >> > >> > >> > >> > >> > >> > On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand >> > <hernan.morales(a)gmail.com> wrote: >> >> Hi Stef >> >> >> >> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >>> Hi Hernan >> >>> >> >>> >> >>> >> >>> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand >> >>> <hernan.morales(a)gmail.com> wrote: >> >>>> I am following the Publishing Pillar Booklet guide from here >> >>>> https://github.com/SquareBracketAssociates/Booklet-Publishin >> gAPillarBooklet >> >>> >> >>> pay attention it is not public because it is in flux because we were >> >>> working on Pillar 70. >> >>> >> >>> Now if you follow the readme of pillar-markup/pillar/ it should work >> >>> since I used it yesterday. >> >>> >> >>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/maste >> r/download.sh >> >>>> $ chmod +x download.sh >> >>>> $ ./download.sh >> >>> >> >>>>./pillar archetype book >> >>> make book. >> >>> >> >>> >> >>> What you should know is that the stable version sucks at the >> >>> infrastructure level (relying on too many servers + silent failures in >> >>> bash files). >> >>> >> >>> Can you retry and let me know? >> >> >> >> Ok I tried again using MinGW in Windows 8.1 >> >> Image is downloaded ok but final step gives an error: >> >> >> >> $ make book >> >> support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY >> (Directory >> >> for build products). Stop. >> >> >> >> I replaced the expanded shell variables in main.mk from using := to = >> >> and it seems to "solve" this problem, though someone else should check >> >> why this happens >> >> >> >> MAIN = $(shell ./pillar introspect mainDocument) >> >> >> >> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) >> >> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) >> >> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect >> latexChapterTemplate) >> >> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) >> >> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) >> >> CHAPTERS = $(shell ./pillar introspect chapters) >> >> >> >> $ make book >> >> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. >> >> >> >> I am using >> >> $ make --version >> >> GNU Make 3.81 >> >> >> >> >> >>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ >> >>> If you want just create your own repo and do >> >>> >> >>> wget https://raw.githubusercontent.com/pillar-markup/pillar/maste >> r/download.sh >> >>> chmod +x download.sh >> >>> ./download.sh >> >>> ./pillar archetype book >> >>> make book. >> >>> >> >> >> >> Thanks, I just followed the install instructions. >> >> >> >> HernÃ¡n >> >> >> >>> >> >>> Stef >> >>> >> >>> >> >>>> $ git clone git@github.com:SquareBracketAs >> sociates/Booklet-PublishingAPillarBooklet.git >> >>>> $ cd Booklet-PublishingAPillarBooklet/ >> >>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/maste >> r/download.sh >> >>>> $ chmod +x download.sh >> >>>> $ ./download.sh >> >>>> >> >>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 >> >>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 >> >>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... >> connected. >> >>>> HTTP request sent, awaiting response... 200 OK >> >>>> Length: 5819 (5.7K) >> >>>> Saving to: 'STDOUT' >> >>>> >> >>>> 0K ..... 100% >> 371K=0.02s >> >>>> >> >>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] >> >>>> >> >>>> Downloading the latest pharoVM: >> >>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip >> >>>> pharo-vm/Pharo.exe >> >>>> Downloading PharoV50.sources: >> >>>> http://files.pharo.org/get-files/50/sources.zip >> >>>> Creating starter scripts pharo and pharo-ui >> >>>> --2018-01-25 17:57:21-- >> >>>> https://github.com/pillar-markup/pillar/releases/download/ >> 50/Pillar-deployment50.zip >> >>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 >> >>>> Connecting to github.com (github.com)|192.30.253.112|:443... >> connected. >> >>>> HTTP request sent, awaiting response... 302 Found >> >>>> Location: https://github-production-rele >> ase-asset-2e65be.s3.amazonaws.com/41843105/f4ea97f0-e63b- >> 11e7-9012-edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X- >> Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1% >> 2Fs3%2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-Ex >> pires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490324f >> 0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&acto >> r_id=0&response-content-disposition=attachment%3B%20filename >> %3DPillar-deployment50.zip&response-content-type= >> application%2Foctet-stream >> >>>> [following] >> >>>> --2018-01-25 17:57:23-- >> >>>> https://github-production-release-asset-2e65be.s3.amazonaws. >> com/41843105/f4ea97f0-e63b-11e7-9012-edab5af1a547?X-Amz- >> Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSV >> EH53A%2F20180125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz- >> Date=20180125T205723Z&X-Amz-Expires=300&X-Amz-Signature=9ecb >> 9c284b9a92c8dbae0c15d8e490324f0fc7ea3cbe98104080f99c4573e1d6 >> &X-Amz-SignedHeaders=host&actor_id=0&response-content-dispos >> ition=attachment%3B%20filename%3DPillar-deployment50.zip& >> response-content-type=application%2Foctet-stream >> >>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com >> >>>> (github-production-release-asset-2e65be.s3.amazonaws.com) >> >>>> 54.231.115.35 >> >>>> Connecting to github-production-release-asse >> t-2e65be.s3.amazonaws.com >> >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)| >> 54.231.115.35|:443... >> >>>> connected. >> >>>> HTTP request sent, awaiting response... 200 OK >> >>>> Length: 18482449 (18M) [application/octet-stream] >> >>>> Saving to: 'imageLn5zD.zip' >> >>>> >> >>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s >> in 8m 7s >> >>>> >> >>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449 >> >>>> (Bad file descriptor). Retrying. >> >>>> >> >>>> --2018-01-25 18:15:46-- (try: 2) >> >>>> https://github-production-release-asset-2e65be.s3.amazonaws. >> com/41843105/f4ea97f0-e63b-11e7-9012-edab5af1a547?X-Amz- >> Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSV >> EH53A%2F20180125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz- >> Date=20180125T205723Z&X-Amz-Expires=300&X-Amz-Signature=9ecb >> 9c284b9a92c8dbae0c15d8e490324f0fc7ea3cbe98104080f99c4573e1d6 >> &X-Amz-SignedHeaders=host&actor_id=0&response-content-dispos >> ition=attachment%3B%20filename%3DPillar-deployment50.zip& >> response-content-type=application%2Foctet-stream >> >>>> Connecting to github-production-release-asse >> t-2e65be.s3.amazonaws.com >> >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)| >> 54.231.115.35|:443... >> >>>> connected. >> >>>> HTTP request sent, awaiting response... 403 Forbidden >> >>>> 2018-01-25 18:15:47 ERROR 403: Forbidden. >> >>>> >> >>>> >> >>>> Also the download speed was super slow. >> >>>> >> >>>> Any ideas? >> >>>> >> >>>> Cheers, >> >>>> >> >>>> HernÃ¡n >> >>>> >> >>> >> >> >> > >> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

Jan. 31, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

Herbert VojÄÃk wrote: > License... ah I forgot to put it there... it'll be MIT. Just added. :-)

Jan. 31, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

License... ah I forgot to put it there... it'll be MIT. Code is, as pointed out in subject, is at https://lolg.it/herby/znock. As I said, beware, wip (but working for simple positive scenarios). Herby Stephane Ducasse wrote: > This cool. Because I wanted to use that in one test with a project with my son. > What is the license? Where is the code? > > On Tue, Jan 30, 2018 at 11:31 PM, Herbert VojÄÃk<herby(a)mailbox.sk> wrote: >> Hi! >> >> I started with a rudimentary HTTP mocking lib (adding features as needed) >> inspired by nock, but using the existing ZnClient / ZnRequest / ZnResponse >> api for mocking. >> >> Atm the feature are very basic (no filtering, matching only by host and >> scheme), but there it is for the interested. >> >> Usage: >> >> setUp >> "other stuff" >> Znock default intercept >> >> tearDown >> "other stuff" >> Znock default verify >> >> testFooBar >> 'https://foo.bar' znock >> url: '/api/ v0/info'; >> get; >> ok: (ZnEntity json: self sampleInfoResponse). >> "code that should get https://foo.bar/api/v0/info" >> >> The setUp starts and cleans the mocker; the test case sets up the >> expectation that GET https://foo.bar/api/v0/info will occur and defines the >> response; tearDown checks that that GET actually appeared and fails if not. >> >> DNU w/ whitelisting is used to reply certain ZnClient messages to set up the >> expectation, ZnResponse class messages to create the response and ZnResponse >> messages to fill it further. >> >> So you can >> >> 'foo.bar' znock >> https; >> url: '/api/v0/info'; >> get; >> notModified. >> >> if you like it this way or >> >> 'foo.bar' znock >> url: '/api/v0/info'; >> get; >> notModified. >> >> to allow both http and https; eventually >> >> 'f oo.bar/api/v0/info' znock >> get; >> notModified. >> >> if you want it shorter; mocking multiple req/res pair should work (not >> tested), as in >> >> 'foo.bar' znock >> url: '/api/v0/info'; >> get; >> notModified; >> url: '/api/v0/last'; >> get; >> ok: (ZnEntity textCRLF: 'herby'). >> >> Both must appear (in any order) for verify to be happy. >> >> Herby >> >

Jan. 31, 2018

Re: [Pharo-users] [ANN] Recording Pharo Techtalk Jan18

by Alexandre Bergel

Thanks Marcus for organizing these events. Alexandre > On Jan 31, 2018, at 7:14 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > The recording and slides for yesterdays TechTalk are available: > > Topic: Genetic Algorithms > > PDF: > http://files.pharo.org/media/techtalk/2018-TechTalk-AI-GeneticAlgorithm.pdf > > Video on Youtube: > https://www.youtube.com/watch?v=ZB1U259wPaA > > (added to the archive at http://pharo.org/TechTalk ) > > Future TechTalks: > > > â¢ Feb 15: Contributing to Pharo 7. > https://association.pharo.org/event-2797065 > > â¢ March 22: Report 2017 Pharo Consortium and Association. > https://association.pharo.org/event-2797067 > > â¢ April 12: Pillar. > https://association.pharo.org/event-2797068 > > â¢ May 17: TBA > > â¢ June 14 TBA > > > Marcus

Jan. 31, 2018

[ANN] Recording Pharo Techtalk Jan18

by Marcus Denker

Hi, The recording and slides for yesterdays TechTalk are available: Topic: Genetic Algorithms PDF: http://files.pharo.org/media/techtalk/2018-TechTalk-AI-GeneticAlgorithm.pdf Video on Youtube: https://www.youtube.com/watch?v=ZB1U259wPaA (added to the archive at http://pharo.org/TechTalk ) Future TechTalks: â¢ Feb 15: Contributing to Pharo 7. https://association.pharo.org/event-2797065 â¢ March 22: Report 2017 Pharo Consortium and Association. https://association.pharo.org/event-2797067 â¢ April 12: Pillar. https://association.pharo.org/event-2797068 â¢ May 17: TBA â¢ June 14 TBA Marcus

Jan. 31, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Stephane Ducasse

This cool. Because I wanted to use that in one test with a project with my son. What is the license? Where is the code? On Tue, Jan 30, 2018 at 11:31 PM, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: > Hi! > > I started with a rudimentary HTTP mocking lib (adding features as needed) > inspired by nock, but using the existing ZnClient / ZnRequest / ZnResponse > api for mocking. > > Atm the feature are very basic (no filtering, matching only by host and > scheme), but there it is for the interested. > > Usage: > > setUp > "other stuff" > Znock default intercept > > tearDown > "other stuff" > Znock default verify > > testFooBar > 'https://foo.bar' znock > url: '/api/v0/info'; > get; > ok: (ZnEntity json: self sampleInfoResponse). > "code that should get https://foo.bar/api/v0/info" > > The setUp starts and cleans the mocker; the test case sets up the > expectation that GET https://foo.bar/api/v0/info will occur and defines the > response; tearDown checks that that GET actually appeared and fails if not. > > DNU w/ whitelisting is used to reply certain ZnClient messages to set up the > expectation, ZnResponse class messages to create the response and ZnResponse > messages to fill it further. > > So you can > > 'foo.bar' znock > https; > url: '/api/v0/info'; > get; > notModified. > > if you like it this way or > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified. > > to allow both http and https; eventually > > 'foo.bar/api/v0/info' znock > get; > notModified. > > if you want it shorter; mocking multiple req/res pair should work (not > tested), as in > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified; > url: '/api/v0/last'; > get; > ok: (ZnEntity textCRLF: 'herby'). > > Both must appear (in any order) for verify to be happy. > > Herby >

Jan. 31, 2018

Re: [Pharo-users] is OSSubProcess working in Pharo 6.1?

by Stephane Ducasse

Thanks I really do not know how to debug it. Because I can load pillar code on my machine. On Tue, Jan 30, 2018 at 11:47 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Stef, > > On 30 January 2018 at 23:13, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Hi >> >> in pillar 70 we have >> baseline: spec >> <baseline> >> spec >> for: #common >> do: [ spec blessing: #baseline. >> spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. >> spec >> baseline: 'OSSubprocess' >> with: [ spec >> repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; >> baseline: 'Mustache' >> with: [ spec >> repository: 'github://noha/mustache:v1.0/repository' ]; >> project: 'Cocoon' >> >> but travis reports this: >> >> >> Fetched -> OSSubprocess-cypress.1 --- >> github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] >> --- github://marianopeck/OSSubprocess:v0.2.5/repository >> Fetched -> OSSubprocess-Tests-cypress.1 --- >> github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] >> --- github://marianopeck/OSSubprocess:v0.2.5/repository >> ...RETRY >> ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is nil >> UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings >> MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: >> >> and I do not get why? >> >> Stef >> > > I use the following to load OSSubProcess in Pharo 7.0 32 bit: > > Metacello new > configuration: 'OSSubprocess'; > repository: 'github://marianopeck/OSSubprocess:master/repository'; > version: #stable; > load. > > > i.e. just replace the "v0.2.5" with "master". > > HTH, > Alistair >

Jan. 31, 2018

Re: [Pharo-users] is OSSubProcess working in Pharo 6.1?

by Alistair Grant

Hi Stef, On 30 January 2018 at 23:13, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > in pillar 70 we have > baseline: spec > <baseline> > spec > for: #common > do: [ spec blessing: #baseline. > spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. > spec > baseline: 'OSSubprocess' > with: [ spec > repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; > baseline: 'Mustache' > with: [ spec > repository: 'github://noha/mustache:v1.0/repository' ]; > project: 'Cocoon' > > but travis reports this: > > > Fetched -> OSSubprocess-cypress.1 --- > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] > --- github://marianopeck/OSSubprocess:v0.2.5/repository > Fetched -> OSSubprocess-Tests-cypress.1 --- > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] > --- github://marianopeck/OSSubprocess:v0.2.5/repository > ...RETRY > ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is nil > UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings > MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: > > and I do not get why? > > Stef > I use the following to load OSSubProcess in Pharo 7.0 32 bit: Metacello new configuration: 'OSSubprocess'; repository: 'github://marianopeck/OSSubprocess:master/repository'; version: #stable; load. i.e. just replace the "v0.2.5" with "master". HTH, Alistair

Jan. 30, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

Herbert VojÄÃk wrote: > Hi! > > I started with a rudimentary HTTP mocking lib (adding features as > needed) inspired by nock, but using the existing ZnClient / ZnRequest / > ZnResponse api for mocking. > > Atm the feature are very basic (no filtering, matching only by host and > scheme), but there it is for the interested. > > Usage: > > setUp > "other stuff" > Znock default intercept > > tearDown > "other stuff" > Znock default verify > > testFooBar > 'https://foo.bar' znock > url: '/api/v0/info'; > get; > ok: (ZnEntity json: self sampleInfoResponse). > "code that should get https://foo.bar/api/v0/info" > > The setUp starts and cleans the mocker; the test case sets up the > expectation that GET https://foo.bar/api/v0/info will occur and defines > the response; tearDown checks that that GET actually appeared and fails > if not. > > DNU w/ whitelisting is used to reply certain ZnClient messages to set up s/reply/replay/ > the expectation, ZnResponse class messages to create the response and > ZnResponse messages to fill it further. > > So you can > > 'foo.bar' znock > https; > url: '/api/v0/info'; > get; > notModified. > > if you like it this way or > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified. > > to allow both http and https; eventually > > 'foo.bar/api/v0/info' znock > get; > notModified. > > if you want it shorter; mocking multiple req/res pair should work (not > tested), as in > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified; > url: '/api/v0/last'; > get; > ok: (ZnEntity textCRLF: 'herby'). > > Both must appear (in any order) for verify to be happy. > > Herby >

Jan. 30, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

Herbert VojÄÃk wrote: > Hi! > > I started with a rudimentary HTTP mocking lib (adding features as > needed) inspired by nock, but using the existing ZnClient / ZnRequest / > ZnResponse api for mocking. Credits: Uses Mocketry's `ZnClient new stub will: ...` to set up mocked client; thanks Denis Kudriashov. Herby > Atm the feature are very basic (no filtering, matching only by host and > scheme), but there it is for the interested. > > Usage: > > setUp > "other stuff" > Znock default intercept > > tearDown > "other stuff" > Znock default verify > > testFooBar > 'https://foo.bar' znock > url: '/api/v0/info'; > get; > ok: (ZnEntity json: self sampleInfoResponse). > "code that should get https://foo.bar/api/v0/info" > > The setUp starts and cleans the mocker; the test case sets up the > expectation that GET https://foo.bar/api/v0/info will occur and defines > the response; tearDown checks that that GET actually appeared and fails > if not. > > DNU w/ whitelisting is used to reply certain ZnClient messages to set up > the expectation, ZnResponse class messages to create the response and > ZnResponse messages to fill it further. > > So you can > > 'foo.bar' znock > https; > url: '/api/v0/info'; > get; > notModified. > > if you like it this way or > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified. > > to allow both http and https; eventually > > 'foo.bar/api/v0/info' znock > get; > notModified. > > if you want it shorter; mocking multiple req/res pair should work (not > tested), as in > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified; > url: '/api/v0/last'; > get; > ok: (ZnEntity textCRLF: 'herby'). > > Both must appear (in any order) for verify to be happy. > > Herby >

Jan. 30, 2018