move functional tests to golang

[concaf]

Hi,

Currently, currently all the functional tests being run by make test-cmd are written in shell scripts, which are very difficult to maintain, debug and produce a lot of false positives e.g. #431, etc.

Should we move these to golang for better testing?

(thinking out loud: how about python which has a rich set of testing libraries e.g. py.test)?

Thoughts?

[kadel]

👍 for writing them in go.

(thinking out loud: how about python which has a rich set of testing libraries e.g. py.test)?

I think it is better to avoid adding new language with additional dependencies, even if it is just for testing.

[procrypt]

@containscafeine @kadel I'm taking this up.

[surajssd]

I am 👍 for Python but it's just that people should know one more language for doing any contribution.

But if you know Python it will be very easier.

[kadel]

Please no Python, no other language.
I would rather stick with bash rather than introducing another language.

[concaf]

Ack, let's move all of 'em to golang 🤘

[surajssd]

maybe we can look at this framework https://github.com/DATA-DOG/godog it is for doing golang functional testing.

[procrypt]

@surajssd Do we really need to use a Framework for it, I mean we are just comparing the output.

[surajssd]

@procrypt not really if we can achieve what we do now without any framework then it's good.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close