can we add fields 'Test step name' and 'expected result' per test step to the test case?

I'm not sure I'm understanding what you are asking here.

You want to add more fields related to the "Steps to execute" of a test case?

yes. So e.g. in below test case 'Set Credit Limit', I have 3 steps in Steps to execute, but the expected result is at the test case level. We want to add test step name and expected result per steps to execute.

or is there any better way to enter test case with multiple steps and each step has expected result, test step name??

Also is there anyway to expend the space for each line under steps to execute as shown in above screen shot? Currently, the words are cut off for each step to display the full content....

It sounds like you have a very specific situation which is unlike that of most "normal" users. It's almost like each of your steps need to be an individual test case with its own steps.

Because your situation is so specific it doesn't really make sense to make this change for all users, but I will leave this thread open for users to vote if they need it.

For the size of the steps to execute, it's something that we've experienced to and want to tackle.

Thanks!

Simon

Hi Simon,

Thanks for the response. Here is my example of one test case in excel format: this is what I'm trying to fit into lean testing. Below 10 steps is for one test case. Are you saying it's best for me to fit below 10 test steps into 10 test cases?? If so, I will need one more hierarchy above the component. Could you please advise how I can best fit below test cases into lean testing? We have a big team waiting to test for our big SAP project. Since we could not find a best way to fit all test cases in, the project deadline has been delayed. Could you please help?

Thanks

Anna

I completely agree with Anna Shen, certainly about the expected result and the size of the test step field - personally, I am not so worried about the 'Step Name'. Could the 'Steps to execute' field, along with the 'Expected results' be moved below the 'Force respondents to submit a screenshot or a video when they complete this test case.' checkbox?

This is standard test methodology. I am writing scripts for others to test and need to be able to explain to them what the expected result of a particular step is, so that they know whether the step has passed or failed.

Maybe it could be added as an option, so that those that don't want it don't have to use it?

Interested to hear your thoughts?

Thanks

:-)

HI Stockers, I completely agree with you. I don't worry about step name either. I think the bottom line is being able to input expected result for each test step. I'm surprised that not so many people brought this requirement up in this forum. I believe being able to input expected result per test step is very standard test script methodology.

Hi Simon, do you think Lean testing will be able to make change for that? we really need to start testing and demo the lean testing to a big team who will perform the testing, but because we cannot find a better way to input test cases, we postponed introducing lean testing to testers and our users from finance team.

Thank you so much for the support.

Anna

Hello Simon/Tech,

We are in the same position as Anna. We need to identify the tool that we will be using, and I would like to recommend this tool to the organisation that I am working in, but I can't until such time as the issues are resolved.

We need to start writing scripts in the next week or so.

Thanks

Stockers

Based on the example posted by Anna above, it really feels like each of these items should be a test case, and not a step. This is further reinforced by the fact that every item that you call a "Step" requires a "Pass / Fail" result.

Here's a good way this would work based on the example above: "Test Step Name" a Component, "Instruction" a Test Case, "Expected Result" the Expected result. That works.

Ultimately, we understand that every company has different requirements and that our tool might not be perfectly adapted to all these requirements. We have to build for the majority of users and sadly cannot make modifications for a single organization. I'm happy to leave this thread open and we'd definitely do something about it if enough users vote for it, but the majority of users are happy with the solution as it is now and have requested other features that we need to prioritize at this time.

Thank you, it's always beneficial to see how users use the tool and how we can make it more useful to them.

I was going to post the same request.  Having experimented with the app for only a couple of days, I have been very impressed so far, but with the one significant limitation that the "Expected Result" field can only be completed at the test case level, whereas most commercial test management programs (HP's QC/ALM etc.) allow an expected result to be defined after each test step. The only workaround at present is to include the expected result along with the steps to execute instruction. If you could allow an expected result against each test step that woule be a huge improvement and would bring Lean Testing in line with most commercial test management tools.

I agree with you Simon, though, only when we have unit tests.

When we have functional tests, we have steps like Anna said, and at each step I need to wait for a result of the step, when I will automate I need to insert asserts and verifys for each step.

Hey Grant, welcome.

But, I've been using leantesting since 2014.

I am feeling that this sensational tool has been discontinued, the 2 weeks that I try to contact in several places and I have no answer.

Thanks, testejoaojunior!  That would be a shame, as I've only just discovered Lean Testing and its intuitive and clean interface is just what I was looking for. If it is no longer supported, I may have to go down the Bugzilla + Testopia route.