Hi Imesh,
Thanks for the feedback on build setup. Its certainly very clean way to
organize a go project. I have incorporated the suggested changes and
updated the readme accordingly [1].
Thanks
Abhishek
[1]. https://github.com/abhishek0198/test-framework
On Wed, Aug 3, 2016 at 11:17 AM, Imesh
On Mon, Aug 1, 2016 at 3:34 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Imesh,
>
> Thanks for the feedback. I completely agree with the naming of executable.
> Unfortunately, go install builds executable using module name and main()
> has to be inside main module name (based
Hi Imesh,
Thanks for the feedback. I completely agree with the naming of executable.
Unfortunately, go install builds executable using module name and main()
has to be inside main module name (based on what I have read so far). A
quick search did not provide any solution so I will tackle this
Hi Abhishek,
On Mon, Aug 1, 2016 at 6:15 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Imesh,
>
> The project is currently structured around standard Golang project created
> by eclipse, you can add eclipse plugin, create a new project with existing
> sources and it should
Hi All,
I have updated the instructions to build and run the test framework [1]. I
am also able to build kubernetes platform on Mac OSX.
[1]. https://github.com/abhishek0198/test-framework
Thanks
Abhishek
On Mon, Aug 1, 2016 at 6:15 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
Hi Imesh,
The project is currently structured around standard Golang project created
by eclipse, you can add eclipse plugin, create a new project with existing
sources and it should compile fine. I will add complete instructions on
Github and update this thread.
Chamila,
The tests I am working
On Thu, Jul 28, 2016 at 4:19 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> 2. I am currently working on adding the ability to run smoke tests from
> the framework. The idea is to have the capability of having product
> specific smoke tests, then teams with more product knowledge
Hi Abhishek,
On Thursday, July 28, 2016, Abhishek Tiwari
wrote:
> Hi All,
>
> We had a meeting on the progress and next steps of Dockerfiles test
> framework. Here are the meeting minutes:
>
> 1. We are currently able to test default and puppet provisioning of
Hi,
Good work so far Abhishek. We'll focus on getting the Kubernetes setup done
soon and test it on that.
Regards,
Vishanth
On Thu, Jul 28, 2016 at 2:49 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi All,
>
> We had a meeting on the progress and next steps of Dockerfiles test
Hi All,
We had a meeting on the progress and next steps of Dockerfiles test
framework. Here are the meeting minutes:
1. We are currently able to test default and puppet provisioning of WSO2
products. I did a test of next Dockerfiles stable release 1.2.0 and did not
find any issue.
2. I am
Hi All,
Another super exciting week of GSoC. I had a meeting with Chamila on Sat
(6/25) and with Vishanth today (6/27). Following are the meeting minutes:
1. We plan on adding smoke tests for individual products (rather than
exhaustive product level tests). The goal is to test the health of
Hi All,
Following are the meeting notes from GSoC Dockerfile test framework weekly
meeting:
*Tasks completed*
1. Ability to check for errors in Docker build and run logs.
2. Added the work around to pass answers to interactive prompt without
having to add silent mode.
3. Working with community
12 matches
Mail list logo