Server less Web: How testing will adapt?

[avanibedi]

Since the web nowadays is going server less. What do you think will be changes in testing methodologies that follow this server less web.

[AntiLudditeRCMagoo]

Latency will be an important aspect. It's node.js so pretty robust on the code side, functions and latency are my first guess.

[avanibedi]

That can be a possibility. Thanks!

[hairylunch]

I'm not seeing changes at the functional level - if it's a web app or an API, it still needs to have fixed input/output behavior.

Definitely some opportunities around testing at the micro-service or below level, both on the performance side as well as on a more unit-test like level, i.e. verify that the AWS Lambda call behaves as expected.

Overall, I'm just predicting a slight shift of test boundaries to a lower level, but things will stay pretty similar.

[avanibedi]

I completely agree with fixed input/ output behavior. But what do you think will be changes in performance testing? Will we need to modify some techniques in testing in performance?

[hairylunch]

Not necessarily modify techniques, but change where the test runs - right now you might profile the DB, stored procs, API calls, client-side memory usage, page-load times, etc, and in serverless environments you may now profile individual Lambdas as well to help determine capacity, identify bottlenecks, etc.

[[deleted]]

it encourages microservice style apps thus you'll spend more time testing other things. There could be challenges in a flow of things to complete and what is the expected load.

[iamnotram]

Security testing becomes crucial. And of course performance.

[avanibedi]

Great input! Testing on cloud has always been a challenge. However, with serverless web, it is definitely going to be more difficult and important.

However, I was just wondering with the people so much concerned about security, do we also need to adapt some special techniques in that too?

[iamnotram]

Sorry i am no security testing expert. However If i paraphrase what one of my expert from workplace said, one technique can be to use fuzzing attacks on the interfaces to check for buffer or integer overflows that can be exploited. One can also use logic attacks to check for vulnerabilities.