why are there so few choices in the types drop down

These are just example.
You can (and should) define your own types...

Test case: Requirement test, Non regression , unit testing. What if it is created for a Ticket?

It is rare (but not forbidden 😉 ) to defined tickets test cases outisde of ticket, mostly of test case is only linked to the ticket.
In most cases, test cases are designed for a development or evolution.
But you can also define complete set of tests cases for your product, and then select one to test a ticket resolution.

Hi there,

I'm trying to get our system of testing now to work on Oria and there are a few things that I don't know where to put.

We have a core test plan made of core test cases, but how to differentiate it from all the other test cases to have it as a whole?

We are using at the moment a

Step | Description | Expected Output |Actual Output |Pass/Fail

table, where the actual output is a screenshot. A test plan has 10-20 steps, and we would want to have the information with the same structure, to be able to export it as a report later.

We were thinking to get the test cases as a test plan of 10 steps, and run test sessions on them, how could we get the Output attached to the steps.
Is the test case the plan, and the test sessions just a test of that test plan, cause that's how we're running it at the moment.

From the documentation it looks like a test case is something very small, like one step in our 10 steps test plan. But we would like to be able to include a test plan in a test case, with a table structure somehow.

Please advise, I have some confused testers 🙁

I hope weather is nice in France this time of the year 🙂

We have a core test plan made of core test cases, but how to differentiate it from all the other test cases to have it as a whole?

Just select a specific type of test. You can define your own.

We were thinking to get the test cases as a test plan of 10 steps, and run test sessions on them

I would advise to set 1 test case per step, and define a parent test case to group then.

how could we get the Output attached to the steps.

Attachment !

From the documentation it looks like a test case is something very small, like one step in our 10 steps test plan. But we would like to be able to include a test plan in a test case, with a table structure somehow.

Yes, test cases should be small.
But they can also be larger, as "parent" to group unitary test cases.

I hope weather is nice in France this time of the year

Unfortunately not. Very wet. 🙁

It is going to be impossible for us to create a test case for each step, the first test of the core test plan has 49 steps, and the whole file today has 118 pages. Just that would make it un-manageable.
right now we describe all steps in description like:
1)step
*expected result
2)step
*expected result
3)step
*expected result
the screenshot for each step are weird to add - a link to a Google doc with slides - one per step.

When you are speaking about making a parent test case, is there another way to define the parenting than adding linked elements? As in can I create a Parent type case which has a different structure?
it belongs to a requirement and has several test cases? Can we define a hierarchy? It all seems to have the same configuration at the moment.

I cone from Lyon, I know how wet it can be, but there's always ski!

Actually, sorry , I set up the parent and the "brothers" predecessor and successor. If these are just for info, what importance have the linked elements?
If I define something as a successor, do I also have to link it?

Thank you for your patience 🙂

is there another way to define the parenting than adding linked elements

Yes : use "parent test case" field (first on treatment part, over "status").
The interest is that if you add the parent test case to a test session, sons test ceses will be automatically added.

is there another way to define the parenting than adding linked elements

Predecessors and successors are there to remind steps that have to be run in a defined order.
Links are mostly for information, to get a quick linlk to an item.
I would not link a test to a test...
But you can link a document to a requirement, an ticket (issue) to a test case, aso.