Comments (6)
Most of the testcases have a short comment explaining the purpose of a test at the top of the source code already, if it's not there you have to look at the test source code. Patches to add short and reasonable description to testcases that miss it are of course welcome.
Also generally you will end up reading the source code for any failing testcases anyway, the comment on the top only helps you to understand the big picture before you dive into the technical details. So there is no point in overcommenting them or in explaining the obvious, etc.
from ltp.
Thanks for your answer ,
I think we need to work on pushing that approach for many reasons.
This will have definitely more than one advantage as follows :
- To track the purpose vs Test case [reviewing and identifying mistakes within test-case]
- To know what are the scenarios missing from a testing point of view [Positive,Negative test scenarios,robustness test ,and missing test techniques]
- To simply the test case analysis in case of failure.
from ltp.
As I said patches are certainly welcome.
from ltp.
Just to make sure i understand you fully , by patches you mean to have a patch file which will override the test case source code [adding the comments], or it's something else ?
from ltp.
Yes, and technically patch does not override source code but rather adds or removes lines.
from ltp.
Thank you
from ltp.
Related Issues (20)
- power_management tests on riscv64
- documentation: Unclear what the difference is between TFAIL and TBROK HOT 2
- mq_open01 fail HOT 1
- cannot find -ltirpc: No such file or directory HOT 1
- ioctl_sg01 testing failure on a specific usb storage
- LTP syscall "migrate_pages03" case will be failed due to infinite loop and timeout when any qemu guest is launched in v6.8 - v6.10 kernel HOT 2
- Write connect() functional test
- Write MREMAP_DONTUNMAP test
- Improve fsconfig test coverage
- Improve fsmount01 test coverage
- Improve fspick01 coverage
- Improve move_mount01 coverage HOT 2
- Improve mount_setattr() coverage
- Improve coverage for open_tree01 testcase
- Adapt loop tests for upcomming 6.11 HOT 1
- kirk documentation in LTP doc
- landlock: test LANDLOCK_ACCESS_NET_BIND_TCP and LANDLOCK_ACCESS_NET_CONNECT_TCP HOT 1
- Write tests for PROCMAP_QUERY ioctl()
- Write test for new MAP_DROPPABLE flag for mmap()
- execve() and creat() syscalls fail - the tests need to be updated HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ltp.