testdat | A package to run unit tests on tabular data

You can indicate that an ISO date is in the UTC timezone by placing Z at the end.

Seems to work:

1. I don't think 20211 is the valid year, do you mean 2021?

2. If you put the function inside User Defined Variables - it will be evaluated only once and won't be random, you should rather inline it into the request body as User Defined Variables are evaluated only once, when the test starts

3. If you're trying to post JSON - I think you should surround the function with quotation marks, otherwise the JSON will be invalid. Suggested change:

Do you just want conditional aggregation:

Your format string is incorrect. It should be:

• core is unstack() month to be columns
• detail then to re-structure month-by month marks columns to required structure
• generally consider bad practice to have duplicate column names, hence have suffixed them

If you want Form2 to access an object you create elsewhere you have to pass the object to form2. Some instance of class X doesn't just magically get access to an instance of Y just because both different places do a new Y and call them the same name, for the same reason that you buying an iPhone and your brother buying an iPhone of the same model and specification, doesn't mean you can read his messages

Now I want to convert it into Europe/Berlin time. But not as a String, I want it as Javascript Date.

That is not possible. The JavaScript Date object does not contain any time zone information whatsoever. The only thing it contains is a Unix timestamp with milliseconds precision. In other words, the Date object encapsulates the number of milliseconds since 1970-01-01 00:00:00.000 UTC (not counting leap seconds). You can see this value directly with .getTime(), .valueOf(), or by any mechanism that converts the Date object to a Number.

When one observes a Date object and sees a time zone or a value in a particular time zone, that behavior is occurring at runtime in the function itself. For example, the toString function of the Date object uses the local time zone of the computer when it converts the internal UTC-based timestamp to the computer's local time before returning a string that has formatted that result.

Most functions on the Date object work in either UTC or in the computer's local time zone (as described). The only ones that work with other time zones are the toLocaleString, toLocaleDateString, and toLocaleTimeString functions, which will accept an IANA time zone identifier in the timeZone option. Like the toString function, they only use this time zone when generating a string. They do not retain it.

In short, the Date object does not contain a time zone, so what you ask for is not possible.

A couple of other things:

• Don't call console.log directly on a Date object. That behavior is undefined. Some implementations return the value of toString while others return the value of toISOString.

• Don't ever try to add/subtract an offset on a date/time unless you really know what you are doing. In most cases, you aren't adjusting for time zone but are actually choosing a different point in time.

• Yes, Z at the end of an ISO 8601 timestamp means that the date and time presented are in terms of UTC.

After Installing Eclipse and getting the same Error Reports like in IntelliJ. I reinstalled jdk 15.0.2. I reopened the project again in IntelliJ and everything worked fine. IntelliJ recommend imports when I used java.util classes. So I will close this question now. Thank you guys very much for trying to help me with this problem. In the end it was something much easier which fixed the problem.

You can do a left join and create a new column based on whether ActualtestDate is null: