Test-Driven-Development | Just for fun2

I am programming since quite some years now. Until now I was mainly focused on writing "normal" applications which run inside a console or with a GUI, sometimes also applications which interact with hardware components such as sensors / actors / ... During this time I got to know a lot of cool programming principles and tools such as object orientation, modularization, unit-testing, test-driven-development, desing-patterns, code-analysis, ..

Also I have some first experience with hosting a wordpress blog, running static web-sites on a nginx webserver, and writing some small php-forms. But I feel like there is still too much magic in all these web-development topics. And I would like to fill this gap and learn a bit more about all these connected scripting / programming languages and technologies. (Because I hate, when I don't understand how things are working :D :D ) I started with some online "Web-development bootcamp" course at udemy to get a rough overview. This took quite some days now and I think HTML, CSS and Javascript for DOM manipulation / animations are clear to me now. Also I heard a lot about NodeJS and all it's derivate languages and databases like Mongo-DB. But still I feel like there is a lot of things unclear to me.

To get to a better understanding I wanted to development some small web-application. Nothing very special, just some website where you have to login to, are able to generate some data and this data is then persisted into a database and once you login again you are able to see the data again. I first started with developing some classes in Javascript to represent the data in the browser while you are logged in. But I very soon realized that the Javascript which can run inside the browser is very limited and already for unit-testing and modularization into separate files that include each other I actually needed to do some crazy work-arounds or use other server-side languages like nodejs / php / ... . After some time coding I decided to take one step back, trying to understand the basic design patterns of web-applications and not running for a long time into the wrong direction.

My questions are:

• Is there some typical way to go / best practice while developing web-applications?
• What are the typical key players? I know there is the difference between front-end, back-end and databases.
• But are there some do's and don't's that good WebDev's follow? For example:
  • which code is usually written in back-end / server-side languages?
  • What is usually done in the front-end? (Only desing and animations?)
  • Do I have to move all business logic into the back-end, also for security reasons or is this maybe also a bad idea because of peformance reasons?
  • What programming languages are more or less dead and not to be used in the future?
  • What things are typically reused from frameworks, for example authentication and session handling?

Also I felt like some things I know from other programming languages are not so easy in languages like javascript / nodejs. I am willing to spend time and effort into learning all these things but I would also like to keep the quality standards that I know from C++ / Python. On the other side I also wondered if these patterns that I have in my head are maybe just boundaries that are completely useless in modern web-development? (e.g. typing, object orientation, modularization / splitting the code to be very reusable )

What do you think am I on the wrong track here, or do I maybe simply use the wrong languages?

I hope the long text is not knocking everyone down / keeping everyone from answering me :o I would really appreciate your help and guidance to understand everything a bit better and to not repeat the things already a lot of others have done wrong ;)

BR, mezorian

I am trying to test the endpoints for my API by using this guide. Specifically, this block is supposed to test the get request:

I'm trying to have a dropdown on a navbar item. It works, but the arrow is over the text of the menu item.

Codepen:

https://codepen.io/ogonzales/pen/QWjmorP

Code

I am trying to run my first migration which creates a single table in a Heroku postgres database.

When I try to run knex migrate:latest --env development I receive the error

Error: Unable to acquire a connection

Things I've tried:

• adding ?ssl=true to the end of my connection string stored in process.env.LISTINGS_DB_URL as I'm aware this is sometimes a requirement to connect with heroku
• setting the env variable PGSSLMODE=require

I also stumbled across this article where someone has commented that knex will not accept keys based on environment. However, I'm attempting to follow along with this tutorial which indicates that it does. I've also seen numerous other references which re-enforce that.

I'll also add that I've been able to connect to the database from my application and from external clients. I'm only encountering this error when trying to run the knex migration.

Furthermore, I've tried identifying how I can check what is being sent as the connection string. While looking at the knex documentation:

How do I debug FAQ

If you pass {debug: true} as one of the options in your initialize settings, you can see all of the query calls being made.

Can someone help guide me in how I actually do this? Or have I already successfully done that in my knexfile.js?

Relevant files:

I'm new using python on kubuntu. I'm writing some simple functions and write also tests on pytest to practise test-driven-development (although I know it's wasted on such easy functions, it's just for the sake of practice).

Because I'm beginner, I'm writing the code in an editor and I'm executing it on the terminal, in a next step I'll use an IDE like Thonny. I have installed Python3.7, although Python2.7 seems to be the standard within the system. Nonetheless, the file with the functions works fine. I'm printing some f-strings and it works fine also. The first line of the file is a Shebang which tells the interpreter, to use Python3.7 (#!/usr/bin/env python3.7). However, when I want to execute the tests, I'm writing pytest in console, as indicated by the pytest-introduction. Alas, I get a syntax error, because it seems that pytest is importing Python2.7 which of course doesn't know f-strings.

I verified that pytest is indeed importing Python2.7 by executing the command pytest --version and I was confirmed.

My question is: How can I make pytest to import Python3.7 so the test would pass or at least the Syntaxerror would go away? Replacing the f-string with a normal string makes the test pass, so I'm assuming this is the only problem.

Any help is highly appreciated. Many thanks in advance. I hope, I gave all the relevant informations. If more information is needed, I'll provide that gladly.

I have set up my environments as described here: https://medium.com/developer-circles-lusaka/how-to-write-an-express-js-server-using-test-driven-development-921dc55aec07

This means I am using the config package to select an environment.

What I would like to do is (re-)populate the database before each test is performed. I am expecting this can be done using the beforeEach() hook Mocha provides (I am using Mocha as a test runner).

My question is to what is an effective way of loading a bunch of data into the database all at once (I am using Mongoose in case that makes a difference. I do not know if I can omit that when inserting)? Preferably this is done in a separated file from the test.

I'm getting the following error when unit testing for a single item using knex. I'm also referencing this https://mherman.org/blog/test-driven-development-with-node/

It renders api/users/1 successfully. So not sure why it says null.

GET /api/users/:id Should return a single show : Uncaught TypeError: Cannot read property 'should' of null at should (tests/users.spec.js:59:26)

users.spec.js

I am trying to implement a basic testing framework in Matlab as my first attempt at Test-Driven-Development. One of the tests I am trying to create is intended to verify that my function throws a specific warning under certain input conditions. My code is passing the warning-related tests as intended, however there is a huge annoyance.

When running (and passing) tests involving the "assertWarning" or "verifyWarning" functions, the warnings that are supposed to be triggered are printed to the command window and visually disrupt the printout of my test suite. Is there a way to prevent the (desired) warning from printing to the console only when being run in the tests, while still verifying that the warning is triggered? A sample test function which causes this annoying warning printout is below.

I want to write a gin middleware handler which gets data from c.Request.FormValue("data"), unmarshalls it into a structure (structures are rather different) and sets a variable in context (c.Set("Data",newP)). So I searched and wrote this: